Benefits of using a traceability matrix document
Filed Under Benefits, Template, Document, Techniques, Process, Development | Posted on December 4, 2007
Benefits of using a Software Traceability Matrix:
How Does having a Traceability Matrix make it far more likely that the proper software cycle is followed ?
- Using a traceability matrix demonstrates the clear relationship between design inputs and design outputs
- Using a traceability matrix ensures that the design is based on established requirements
- Using a traceability […]
Software Traceability Matrix
Filed Under Benefits, Document, Process, Development, Software | Posted on November 27, 2007
What is a Software Traceability Matrix ?
Sounds like a big word; it is actually a way to trace that all the requirements have been mapped through the development cycle. For example, that the various sections of design have covered all the requirements, test plans and cases cover all the requirements and so on. The traceability […]
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 […]
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 […]
Benefits of Use Case Modeling
Filed Under Document, UML, Benefits, Design, Techniques, Development, Model, Software | Posted on October 22, 2007
Use Case Modeling takes effort and time, and requires a certain degree of expertise. Why do we do Use Case Modeling then ? What are the benefits of such an approach ?
Use cases are an effective technique for capturing and communicating functional requirements. Use cases provide some very clear benefits to the Analysis Phase.
- One […]
Software coding standards - what, and why !!
Filed Under Document, Benefits, Coding, Techniques, Improvement, Development, Terms, Software | Posted on October 13, 2007
What is source code ?
Source code is what makes the application. It is source code that gets compiled and becomes the software application that you see. In computer science, source code (commonly just source or code) is any sequence of statements and/or declarations written in some human-readable computer programming language. A computer program’s source code […]
Benefits of a code review
Filed Under Techniques, Benefits, Review, Improvement, Model, Development, Process, Software | Posted on October 6, 2007
Why would you get a development team to do a code review ? What is in it for them ? It takes time to fit in a code review, and the basic principle could be an affront to a confident developer that his/her code, written with a lot of skill, needs to be reviewed by […]
What is a code review ?
Filed Under Techniques, Benefits, Review, Improvement, Terms, Development, Process, Software | Posted on October 4, 2007
For many types of work it is standard practice to have one’s work checked by another before the work product is put into service. Engineers have inspectors, writers have editors, and so on. But in software development it is common for code to flow directly from the programmer’s fingertips into the hands of the end […]
Benefits of UML and some goals
Filed Under Architecture, UML, Benefits, Design, Techniques, Development, Process, Software | Posted on September 29, 2007
Why was UML made ? The primary goals in the design of the UML were:
- Provide users with a ready-to-use, expressive visual modeling language so they can develop and exchange meaningful models.
- Provide extensibility and specialization mechanisms to extend the core concepts.
- Be independent of particular programming languages and development processes.
- Provide a formal basis […]
