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 […]
Problems faced in the stage of Requirements Analysis
Filed Under Document, Requirements, Issues, SDLC, Development, Software | Posted on October 17, 2007
For a process that is so critical to the success of a software project, you would be surprised at the number of problems that can happen during the requirements gathering and analysis process. This must be the reason why Requirements Analysis is called the ‘make-or-break’ step of any project.
* Users don’t understand what they want […]
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 […]
Details about Requiements Analysis
Filed Under Terms, Document, Model, SDLC, Development, Process, Software | Posted on October 17, 2007
What is Requirements Analysis ?
Requirements are a description of how a system should behave or a description of system properties or attributes. It can alternatively be a statement of ‘what’ an application is expected to do. Requirements drive almost every activity, task, and deliverable in a software development project. Requirements must be actionable, measurable, testable, […]
Problems in trying to implement coding standards
Filed Under Standards, Coding, Document, Process, Software | Posted on October 13, 2007
Coding standards sound like the best thing possible; they help in getting uniformity, they enable easy transition, they promote easy code review and preparation of documents such as SDK’s, and so on. So why would you not be able to get coding standards implemented across development teams ?
Mostly it is due to individuality. Most developers […]
Coding standards for different languages
Filed Under Coding, Standards, Document, Process, Development, Software | Posted on October 13, 2007
Nowadays code can be written in a number of different platforms and architectures. For example, earlier, you would have primarily C and C++ as the different languages in which code was written for a majority of applications, but now there are so many different languages and platforms that the same coding standards cannot be used […]
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 […]
The software architecture design process
Filed Under Document, Architecture, Design, Techniques, Model, Software | Posted on September 24, 2007
Early attempts to capture and explain software architecture of a system were imprecise and disorganized - often characterized by a set of box-and-line diagrams. During the 1990’s there was a concentrated effort to define and codify fundamental aspects of the discipline. Initial sets of design patterns, styles, best practices, description languages, and formal logic were […]
High Level Design Document Template
Filed Under Design, Document, Techniques, Terms, Development, Model, Software | Posted on September 20, 2007
The High Level Design Document is a pretty important document for a project, covering at a high level the overall design of the solution. If one were to try and present a very succinct summary of the High Level Document, it could be something like this:
- Detailed use case scenarios of key process flows of […]
Basic objective of a High Level Design Document
Filed Under Document, Design, Techniques, Model, Development | Posted on September 20, 2007
High level software design, also called software architecture is the first step to analyze and consider all requirements for a software and attempt to define a structure which is able to fulfill them. For this also the non-functional requirements have to be considered, such as scalability, portability and maintainability. This first design step has to […]
