0
For developing systems/software that involves 10 Phases:
1. Initiation
2. System Concept Development
3. Planning
4. Requirements Analysis
5. Design
6. Development
7. Integration and Testing
8. Implementation
9. Operations and Maintenance
10. Disposition.
The Phases
Initiation - Initiation is where there is an identified need for a new system. For instance, a retailer of fine crystal glass is in need of a new system to handle inventory. They've decided that the old System of putting the inventory into a simple spreadsheet will no longer work. They want a system where they can track inventory, inventory cost, facilities cost, personnel, a customer database, can track trends in buying, identify inventory that is not moving well and price it to move, etc. In other words, they want to be able to know everything with a few clicks of the keyboard. A Project Management is placed in charge and he/she will develop a Concept Proposal - which is a document identifying the problem and why the new system needs to be pursued. The document is presented to upper management who approves it and the project moves on to the next phase.
System Concept Development - This is where the first real look at what will be necessary takes place. Several reports can be created here.
- Feasibility Study (will it work?)
- Cost/Benefit Analysis (is the cost really worth it?)
- System Boundary (how far should the project go?)
- Risk Management (what will happen if we don't do it?)
These reports are then presented, again, to the powers that be and a decision is made whether or not to go ahead. They approve the funding. If they give their approval it's on to the next phase.
Planning Phase - Who is doing what, when, and how? What personnel are needed? Use existing personnel or hire consultants? New Hardware? Develop own software or buy it off the shelf? What are the Deliverables - such as completed software programming and documentation, user manual, training, testing plans, etc? A Planning document is submitted for approval.
Requirements Analysis - Documentation of requirements. What interfaces are required (will it run with Windows NT and Windows XP?). What is the functionality required - should it be run with the mouse or keyboard commands? What is the level of proficiency required by the user? Will a new room be needed for the servers or equipment? Requirements documentation is approved, then it's on to the Design phase.
Design Phase - Take those Requirements and develop detailed, workable specifications. This is where everything is put together and the actual design of the system is done. This is also where documentation such as the Maintenance Manual, Operations Manual, and Training Manual begin. This is also where some of the flaws in the original planning may appear and require some adjustment. Again, there is documentation and approval.
Development Phase - The system is built. The software, hardware, and testing occur during the Development Stage. This is also the phase where the bugs are worked out of the system. A contingency plan is also developed at this point. A contingency plan is an emergency management document. If the power goes out - what happens to the system? What is the back up? How fast can it be brought back up to speed? Again, documentation and approval (get used to this).
Integration and Testing Phase - This is the formal integration and testing of the system. Testing has been done on the development phase, but in the Integration and Testing Phase it is a formal, documented testing procedure, not only to assure that the system performs as designed, but testing the roll-out of the system. If there is already another system in place with data, how fast can that data be migrated into the new system and useable to the company? Usually, the system is rolled-out over a weekend so that if anything goes wrong, the old system is still active and available. Integration and Testing is vital to the decision to go "live" with the new system. If it fails testing, it cannot be
trusted to work. Approval of testing and test results is necessary before the project moves into implementation.
Implementation Phase - Everything is ready and it's time to go live. Training takes place, everyone who will use the system must be fully informed of the day it goes live, previous data is migrated, and the system is ready for use. After it goes live, the system is reviewed post-implementation to see how well it worked and how well did the project go. It's often known as a debriefing or lessons learned meeting. It is also where any problems that were not crucial to the implementation can be addressed and any necessary changes to the system documented for future versions.
Operations and Maintenance Phase - Hey, it's not over. Just like a car engine, maintenance and support are necessary. What happens if the system is based on Microsoft NT 4.0 and 2 years later Microsoft is no longer supporting NT 4.0? Or, a new e-mail program is put in place and it interferes with the system? Fixes are necessary and will occur. This is the day-to-day operation of the software. No one can just walk away once the software is rolled-out and say, "Whew, glad that's over." It's not over; it's just begun.
Disposition Phase - This is where the system has become obsolete. Perhaps a whole new system is coming in, or this system cannot keep up. Many programs and systems became obsolete with the Y2K problem or with upgrades of operating systems. Whatever the reason, putting the system to bed involves more than just shutting off the server. Often, the system may be kept going due to regulatory issues or because there are still projects using it. Even if the system will be shut down due to the development of a better system, disposition needs planning. A disposition plan, archiving of system documentation, archiving of data, even a plan for getting rid of the old equipment may be a part of the Disposition Phase.
This is a short description of SDLC and its phases. The important idea to take away from SDLC is that it involves planning, approval, testing, and documentation to assure that the system can, and will work as required.
What else can I help you with?
What were the three phases of northern industrialization?
the three phases of industrialization are : 1.division of labour 2. labour that has developed specialization during the first phase, gather into a collective setting 3.in the third phase , industrialization capitalizes on the basis of first two phases.
Matrix is an aid to trace requirements across different phases of development?
kncsJVKS;
What ipde stand for?
Identify, Predict, Decide and Execute
What are the three historical phases of the Industrial Hygiene profession?
Historically, the industrial hygiene profession was described as the art and science of the recognition, evaluation, and control of hazards in the workplace. To those three elements or phases, the concept of "anticipation" was added in the 1970s, so there are now four phases:anticipationrecognitionevaluationcontrol
How do you identify asbestos insulation?
The only way to reliably identify asbestos-containing insulation is to have a small sample analysed by a qualified laboratory.
Which phases of SDLC can be sources of error?
Actually - all phases of SDLC can be a source for Errors. The later in the life cycle an error is detected, the costlier it will be to fix it
Which phases of SDLC can be sources of errors?
Actually - all phases of SDLC can be a source for Errors. The later in the life cycle an error is detected, the costlier it will be to fix it
What are the five phases of the sdlc?
The five phases of the Software Development Life Cycle (SDLC) are: Requirements gathering, Planning, Design, Implementation, and Maintenance. These phases guide the development process from initial concept to final product delivery, ensuring a structured approach to software development. Each phase contributes to the overall success of the project by systematically managing tasks and resources.
Which phase of sdlc can be sources for errors?
Actually - all phases of SDLC can be a source for Errors. The later in the life cycle an error is detected, the costlier it will be to fix it
What is the important of sdlc?
SDLC or System Development Life Cycle is important because it describes the phases that a program developer has to follow to ensure success. The cycle consists of between four and seven steps that a programmer should adhere to in his work.
Systems Development Life Cycle on library management system?
The SDLC has 4 phases that are used when developing a library management system. Those phases are planning and selection, analysis, design, and implementation.
Which Phase of SDLC can be sorces for error?
Errors can originate in several phases of the Software Development Life Cycle (SDLC), but they are most commonly found during the requirements gathering and design phases. Inaccurate or incomplete requirements can lead to misunderstandings, resulting in a product that does not meet user needs. Additionally, design flaws can introduce fundamental issues that are costly to fix later on. Therefore, thorough validation and verification in these early phases are crucial to minimize errors.
What are the advantage and disadvantage of system development life cycle?
Advantages The project mangers and programmers will able to communicate to each other Components will be easier to define Uncompleted products can be passes on to another person when necessary
Sqa roles and document in SDLC?
In the Software Development Life Cycle (SDLC), Software Quality Assurance (SQA) roles focus on ensuring the quality of the software throughout various phases. SQA professionals are responsible for developing and implementing testing strategies, creating and maintaining documentation such as test plans, test cases, and defect reports, and conducting reviews and audits. Their objective is to identify issues early, ensure compliance with standards, and facilitate continuous improvement in processes and products. Effective SQA practices contribute to delivering high-quality software that meets user requirements and minimizes risks.
Which phases of sdlc can be sources for errors rs design cut?
Errors in the Software Development Life Cycle (SDLC) can stem from several phases, particularly during the requirements gathering, design, and coding phases. In the requirements phase, misunderstandings or incomplete specifications can lead to fundamental issues in the design. During the design phase, poor architectural choices or inadequate design documentation can introduce flaws, while the coding phase may introduce syntax and logic errors. Effective validation and testing in later phases are essential to catch and address these errors before deployment.
Where can you identify the different phases of water?
You can identify the different phases of water in its solid form as ice, liquid form as water, and gaseous form as water vapor.
Which phaseof sdlc can be sources for errors?
Errors can originate in multiple phases of the Software Development Life Cycle (SDLC), but they are most commonly found during the requirements gathering phase, where misunderstandings or incomplete specifications can lead to flawed designs. Additionally, the design and coding phases are critical, as poor design choices or coding mistakes can introduce significant issues. Testing is also a phase where errors may be identified, but if previous phases were not conducted thoroughly, it may be too late to address foundational problems effectively. Regular reviews and quality assurance throughout all phases can help mitigate these risks.
