In this article, we discuss the system development life cycle and tie it in with professional skills needed at each stage. We go through an overview of the system development life cycle to show learners where they’ve been and where they’re going in the process of designing and creating a database.
- List and describe the different stages of the system development life cycle (SDLC)
- Identify the role of data modeling in the SDLC
- Relate the project tasks to the different stages of the system development life cycle
- When you build a house, you draw up the plans before you start construction.
- During construction, you lay the foundation before you start putting up walls. You finish all the major construction before you start decorating.
- The architect, the builder, and the decorator coordinate their efforts so that they do their jobs at the appropriate times.
- A knowledge of the tasks associated with each stage of the system-development life cycle will help you better plan a project and be a productive member of the team.
The system development life cycle is quite common in the business world.
Although the names of the stages may change (some will call it planning instead of strategy, etc.), the tasks and the sequence remain largely the same.
System Development Life Cycle
- You can develop a database, from concept through production, by using the system development life cycle (SDLC) for software development.
- Applying this top-down, systematic approach to database development transforms businessinformation requirements into an operational database.
System development life cycle: The process of developing information systems through a multi-step process.
Some diagrams will have documentation as part of build. In reality, documentation should really be a part of every stage
Strategy and Analysis
- Project tasks at this stage of the Systems Development Life Cycle (SDLC):
- Study and analyze the business requirements.
- Interview users and managers to identify the information requirements.
- Incorporate the enterprise and application mission statements as well as any future system specifications.
- Build conceptual models of the system.
- Transfer the business narrative into a graphical representation of business-information needs and rules.
- Confirm and refine the model with the analysts and experts.
Project tasks in the design phase:
- Transform the model developed in the strategy and analysis phase.
- Map entities to tables, attributes to columns, relationships to foreign keys, and business rules to constraints.
In the design phase, we create table diagrams, not actual tables. At this stage, several implementation issues will be taken into consideration, such as type of database, storage, location of the database (centralized or distributed?), the way the data is used, etc.
These types of considerations affect decisions such as supertype/subtype implementations, where to put the foreign key in a 1:1 mandatory relationship, etc.
Project tasks in the Build phase:
- Write and execute the commands to create the tables and supporting objects for the database.
- Populate the tables with data.
- Develop user documentation, help text, and operations manuals to support the use and operation of the system.
This is also the stage where applications (screens, reports, web pages, etc.) are built to run with the database.
Transition phase tasks:
- Conduct user-acceptance testing.
- This type of testing is where monitored users determine whether a system meets all their requirements, and will support the business for which it was designed.
- Convert existing data
- Parallel operations.
- Both systems (old and new) are running at the same time. This is done to give users time to train and switch over to the new system and to check that the new system is producing the same results as the old system
- Make any modifications required.
User-acceptance testing involves having the users try out the system and provide feedback on the interface, compare it with the old system, etc. This feedback is used to tweak the system – make a few adjustments to satisfy the users.
Existing data often has to be converted for several reasons: the database system uses different formats, the new database design requires that the data be broken down into more detail or summarized into group totals, the new system tracks data that did not exist in the old system but can be derived somehow, etc.
- Production phase tasks:
- Roll out the system to the users.
- Operate the production system.
- Monitor its performance and enhance and refine the system.
- The various phases of the system development life cycle can be carried out iteratively.
Key terms used in this tutorial included:
- Parallel operations
- System development life cycle
- User acceptance testing
In this tutorial, you should have learned how to:
- List and describe the different stages of the SDLC
- Identify the role of data modeling in the SDLC
- Relate the project tasks to the different stages of the SDLC