Software Configuration Management: Best Practices
Filed Under Document, Benefits, Design, Techniques, Development, Process, Software | Posted on November 27, 2007
Software Configuration Management can be a complex science. Given that SCM requires setting up of a number of processes, and procurement of expensive software and hardware, optimization is necessary. Towards that end, defining some Best Practices for Software Configuration Management is always a good idea.
* Identify and store artifacts in a secure repository: To do […]
Software Configuration Management Tools
Filed Under Tools, Process, Development, Software | Posted on November 20, 2007
Okay, now you know all about what Software Configuration Management actually is (or think you do !); what are the tools that can help you in this regard ? There are a fair number of tools that can help, ranging from professional tools that can cost a decent amount to open source tools that are […]
The process of Software Configuration Management
Filed Under Document, Techniques, Process, Development, Software | Posted on November 7, 2007
SCM is not one of the easiest of things to easily explain and understand. It is easiest to understand if you have been in a situation where SCM is required, and more, important been affected by not having a SCM process in place. Configuration management is a complex undertaking, embracing a number of disciplines. The […]
Goals and benefits of Software Configuration Management
Filed Under Benefits, Techniques, Process, Development, Software | Posted on November 2, 2007
Why do we need to use Software Configuration Management (SCM) ? What are the goals and objectives of this process ?
The main goal of SCM is to identify, control, maintain, and verify the versions of software configuration items. An SCM solution tries to meet the following goals:
* Account for all the IT assets and configurations […]
Software Configuration Management - Definition
Filed Under Techniques, Review, Terms, Process, Development, Software | Posted on November 1, 2007
One definition of Software Configuration Management is a set of activities designed to control change by identifying the work products that are likely to change, establishing relationships among them, defining mechanisms for managing different versions of these work products, controlling the changes imposed, and auditing and reporting on the changes made. In other words, SCM […]
Use Case Template
Filed Under UML, Template, Document, Process, Development, Software | Posted on October 28, 2007
There is no standard template for documenting detailed use cases. There are a number of competing schemes, and individuals are encouraged to use templates that work for them or the project they are on. Of course, there are many Use Case Templates that are available on the internet, so here’s a listing:
Formal Use Case Template, […]
Understanding various terms in Use Case Modeling
Filed Under Design, Document, Techniques, Terms, Process, Model, Development | Posted on October 28, 2007
There would be few people in the world of software development who would not have heard of Use Case Modeling, but the number of people who know details about a Use Case would be far fewer. So let’s try and see what the various parts of Use Case Modeling are.
A use case is a technique […]
What is Use Case Modeling ?
Filed Under Design, Document, UML, Terms, Model, Development, Process, Software | Posted on October 22, 2007
What are Use Cases and what is Use Case Modeling ?
A use case is a technique used in software and systems engineering to capture the functional requirements of a system. Use cases describe the interaction between a primary actor—the initiator of the interaction—and the system itself, represented as a sequence of simple steps. A Use […]
Software Requirement Specification (SRS) template
Filed Under Document, Requirements, SDLC, Process, Development, Software | Posted on October 17, 2007
Given the importance of capturing the Requirement specifications in a well documented way, the document itself should be very well drafted. The sections in it must closely map to the needs, and yet the overall document must not be very process heavy. It should make sense to the stakeholders, and yet capture all the relevant […]
Requirements Analysis Process
Filed Under Requirements, Document, Process, Development, Software | Posted on October 17, 2007
There is a lot of talk about how Requirements Analysis should be thorough, capture all the user requirements (including from ‘real’ users), and if possible, the requirements analysis process should ideally be part of an iterative loop so that there are no requirements that are missed out (given that in the normal waterfall model, there […]
