What are the documents involved in the SDLC?

Question

From pricing to delivery - despite the software development life cycle,

• What are all the documents involved and
• What is the order?

I’m not sure if the methodology has a big impact on the documents, one way or another we’ll look at the Waterfall.

Answer 1

The answer - as was said - it depends. I am sure that many people will be responsible for the Agile methodology (which is a much more moving holiday), so for completeness I will go with what you would have for the standard standard waterfall methodology:

• A document with an area is a very high level, setting out, more importantly, what is not within the scope of the project and what assumptions are being made. The main purpose of this document is to establish expectations for what will ultimately be delivered - you do not say how everything will work, but you try to answer questions such as whether there will be messages? Will it transfer data to other systems? Will you write your own user management features or pull out of AD? If you cannot get specific answers to these questions, include the assumptions section and list what you are suggesting, so that people can correct you if you are wrong. It should also include things such as dates for achieving the goal (and not as a commitment, but people know what is expected and manage expectations accordingly).
• Functional specification . What the application should do at the business level. This can be divided into business requirements (business processes that it automates and how they work) and functional requirements (what the system does and how it does it - on-screen navigation, calculation methods, etc.), but more often they are combined, with the exception of the largest systems. It should also include “non-functional” requirements, such as performance, loading, security, etc.
• Technical specification Most likely to be skipped. Detailed technical design, including objects such as object models, diagrams, and information on how detailed technical problems are handled.
• Test plans and test cases . How an application is tested with detailed test cases, data and expected results, covering all elements of the system.
• User Guide and Release Notes . How to install, configure and use the application.

I would add that this is a support document - a short (less than 10 pages) crash course in what the application does and how it does it. Developers often don’t read the full specifications (either because they don’t have time or don’t want to), so this document should be enough to understand what it does, how it works, areas of the application that are most likely to be problematic etc. It would be written a few weeks after you went to live as a team that built and implemented the system.

Of course, depending on your methodology, you may not have any of these documents, but if you use a standard project in an old school structured, waterfall road, it will be pretty normal.

Answer 2

I will use a typical advisory answer ... "It depends."

To get started, the methodology has a huge impact on documentation artifacts (not to mention the success of the project), and I would put the project management in the style of a waterfall at the same level as letting my doctor cover me with leeches to cure a broken leg.

That said - I saw people using the Microsoft Solutions Framework, and here is a link where you can capture your templates:

http://www.microsoft.com/downloads/details.aspx?FamilyID=9D2016AD-6F8A-47F5-84FA-BEC389DB18C1&displaylang=en&displaylang=en

In reality, I would strongly recommend that any project use Agile methodologies and engineering practice (at least if you want it to have a much higher chance of success than a waterfall project).

http://www.agilealliance.com/ has a good read, like wikipedia at http://en.wikipedia.org/wiki/Agile_software_development

Good luck

Answer 3

In a typical production scenario, where development is not performed on the client’s site, the SDLC waterfall model is usually used and documents related to the various stages of the WFM are prepared:

• Requirement Collection - A business requirements specification that details the complete requirement. It is functional in nature. This is accompanied by test case scripts provided by users in which users mark those tests and tests that they will perform according to their desired functionality. This serves as a guide for the development team, as well as for empowerment and validation.

• Requirements analysis. At this stage, the BA associated with the project conducted an impact analysis and feasibility analysis. Restrictions, if any, in requirements, restrictions, assumptions are documented, shared by business users and signed in order to avoid further surprises.

• Development Approach. At this stage, the development manager or system analyst prepares a document document that defines the process flow, screen design, controls that will be placed on the screen, checks, attributes, database diagram, etc. This is then written out with BA. If the development team anticipates any technical limitations that will affect the desired functionality, then it will again be transferred to the business team and will be canceled.
• Testing. When users test in a release, they test the release based on test cases and test scripts provided earlier. Defects found are documented and sent back to the development team. First, defects are first checked by the BA to determine if a defect has been detected in understanding defects, functional requirements, or technical errors. Accordingly, a resolution is provided. At this stage, it is necessary to ensure that all test cases are successfully completed and all errors are resolved. If any test case or error is parked for the next run, then base its influence on functionality, the joint call of the development team and business users on the risk involved. In the end, business users prepare a test document for registration, which mentions the time taken by each resource to test, monitor and improve the process.
• Production Deployment — This includes deployment instructions for the deployment team, server administrators, and databases for the deployment.

Feel free to suggest your suggestions.