System Development Life Cycle Phase III – Design

Running head: SYSTEM DEVELOPMENT LIFE CYCLE PHASE III-DESIGN 1

SYSTEM DEVELOPMENT LIFE CYCLE PHASE III-DESIGN 2

System Development Life Cycle Phase III – Design

Student’s name

Professor’s name

Course title

Date

System Development Life Cycle Phase III – Design

The system development cycle is a process that involves conceptualizing, building, implementing, and improving software or hardware. The system development cycle should consider both security concerns and end user requirements in all its phases. The system development lifecycle is made up of planning, analysis, design, implementation, testing & integration, and maintenance (Stair, 2017). This paper will focus on the design phase.Top of FormBottom of Form

Phase III – Design

The system design phase takes place after thoroughly comprehending the customers’ requirements. Design phase describes system elements, components, architecture, security levels, modules and the various interfaces as well as kind of data which via the system. It changes the specifications of software into a design plan (Stair, 2017). The plans are stipulated with regards to hardware, architecture, programming, OSes, security and communication issues.

System design includes the design of network, databases, user interfaces, applications; transform the SRS documents into logical structure which contain complete specifications and detailed that can be implemented in a programming language; create a contingency ,training, maintenance, and operational plan as needed, recheck the proposed layout design, ensure that the final design must meet the requirements as stated in the SRS documents; and prepare a design document which will be used during the next phases (Stair, 2017).

Unlike the analysis, design requires less engineering and mathematics focus so that one can serve the users views. The design process is the most iterative which requires multiple sessions, with users using trial and error method (Langer, 2008). Design requires technocrats in screen architecture, data design as well as the professionals that understand the needs of network servers’ performance and other hardware components required by the system.

Design phase further shows how user requirements will be fulfilled by the system. This can be achieved by physical and logical design. In this scenario, the system design and operates are detailed that is, annotations screen layouts, storyboards, business laws and other documents. The finality of this stage will indicate the new system as modules collection. The training needs, support, and functionality are converted into preliminary and detailed design. Consensus is made to redress how the system will meet general requirements (Kendall & Kendall, 2013). The system design enforces how the function features of the system are produced as a high level guide. A detailed system design that expands the design is produced with the technical details required to develop the system.

The other aspects of system design are the necessities specifications, features, and operations that will satisfy the functionality specifications of the proposed which will be in place. This is the place of the end users to share and discuss their specific business information needed for the proposed system. It is during this phase whereby they will discuss and consider the essential components, processing and procedures for the system to attain its objectives (Vivas, Agudo & Lopez, 2011). Once your done with the plans and you have identified the costs, the system and the users requirements a detailed system design can begin that’s includes features and other documents. The architectures then can build a sample frame work.

The design phase activities encompass selecting the appropriate database management system, system navigation methods, interface designs, data capture design, establishing system security standards, and standards for printed report production. The key deliverables of this phase are function specification documents (outputs, data, process, inputs), technical specification documents (network, programs, files), and implementation schedule. During the design phase, analysts choose the offers and realistic of the highest payoff for the company. The output here is a document with specifications for implementing the system (Bidgoli, 2015). Prototyping is popular in designing system information because needs can change quickly and lack of specifications for the system can be a problem.

Top of Form

The conceptual design objective is to produce alternative system that satisfies the system needs identified during system analysis. By presenting users with alternatives, the system skips imposing pre conceived constrains on the new system. The user will evaluate the models and settle on the alternatives that appear pleasing and appealing. These alternative designs then go to the system selection phase of SDLC where the costs and benefits are compared and single optimum design is selected (Hall, 2015). By keeping system design conceptual throughout these phases of SDLC, we maintain the investment of resources in alternative design that will be denied (Bidgoli, 2015). The conceptual system wins proceeds to the final phase of the SDLC where it is designed in details and implemented.

Conclusion

Design phase describes system elements, components, architecture, security levels, modules and the various interfaces as well as kind of data which via the system. The activities under system design have been discussed. The first two phases have to be completed before moving on to the third phase.

References

Bidgoli, H. (2015). Mis. Boston , MA : Cengage Learning,

Hall, J. (2015). Information technology auditing. Mason, OH: Cengage Learning.

Kendall, K., & Kendall, J. (2013). Systems analysis and design, global edition. Harlow, United Kingdom: Pearson.Bottom of Form

Top of Form

Langer, A. (2008). Analysis and design of information systems. London: Springer.

Stair, R. M. (2017). Fundamentals of Information Systems. Course Technology.

Vivas, J., Agudo, L., & Lopez, J. (2011). A methodology for security assurance-driven system development. Requirements Engineering, 16(1), 55-73.