Traditional SDLC Analysis      Work Group 1: Mohammed Kamil Zakari, Eric Odame, Jay White, Ajiboye JohnsonWith the rapid i...
situations where the system can be well identified up front and when the management does nothave a lot of experience with ...
WG 1 “The Department”                                          “Data Center”Our department used to be the data center of t...
DESIGN AND IMPLEMENTATION PHASEThe Department is Data Center                                                      WG.1 Con...
References:Stair, R., & Reynolds, G. (2011). Principles of information systems. (10 ed.). Course Technology.Kay, R. (2002,...
Upcoming SlideShare
Loading in …5
×

Group 1 itec 630 sdlc review

470 views
415 views

Published on

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
470
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
2
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Group 1 itec 630 sdlc review

  1. 1. Traditional SDLC Analysis Work Group 1: Mohammed Kamil Zakari, Eric Odame, Jay White, Ajiboye JohnsonWith the rapid increase in availability and use of information systems and software among largebusinesses, it became apparent that a standard was needed to systematically and methodicallydevelop systems for the enterprise. The approach that was developed was called the traditionalSystem Development Life-Cycle (SDLC.) The traditional SDLC incorporated several linearsteps to help maintain a methodical and systematic approach to the development of informationsystems. The steps included are; feasibility study, requirement/system analysis, system design,system development, system implementation, system testing, and maintenance. The SDLCbegins with the feasibility study, in which the project is defined with high-level objectives, andan initial set of goals is determined. With the project defined the SDLC moves into therequirement analysis. This is where information is gathered to help better define the goals andneeds of the project. The end-user is a vital component of this step, as it is here that their needsare defined and documented. Once the user’s needs have been defined, the system can bedesigned. This process will include details about the system, diagrams detailing the system, andeven pseudo code that may be used in the development of the system. The system is thendeveloped to ensure that everything is functioning according to the goals and requirements thatwere established early on in the process. If everything is functioning properly it is time toimplement and then test the system. The maintenance of the system is where the system willremain for the rest of its lifecycle, and can include changes and upgrades to the system. Thetraditional SDLC focuses on strict management of the project with target dates, budgets, and theimplementation of the system tightly controlled and followed. This type of SDLC is best used in
  2. 2. situations where the system can be well identified up front and when the management does nothave a lot of experience with developing a system. This type of SDLC also works very wellwhen implementing a newer version of a system that is already in use, or when quality is moreimportant than time and budget. Pros ConsThe amount of documentation required helps The excessive documentation can cause delaysto ensure a quality and reliable system. and be expensive and cumbersome.The strict control used in the traditional SDLC The strict control causes this SDLC to not behelps to ensure timely production. flexible to change and the needs of the users.The user’s needs are identified up front and With the user’s needs identified up front, theused to design the system. users don’t typically get to use the system until it is implemented.Project milestones are well understood and The linear nature of this SDLC can causeidentified from the beginning. rigidity in the process, restricting flexibility. Figure 1
  3. 3. WG 1 “The Department” “Data Center”Our department used to be the data center of the ABC Associates for several years off-site andwe have been bought over to WG.1 Conglomerate. We are still going to be off-site but we are inthe process of interfacing our LAN to WAN with the new parent company, WG.1 Conglomerate.REQUIREMENTS ANALYSIS PHASE 1. The New parent company wants us to interface with them through VPN tunnel which will extend our reach and also includes security instead of the Dark fiber or private link 2. WG.1 Conglomerate wants switches on our LAN and on their end 3. Type of access should be Unidirectional 4. WG.1 Conglomerate needs us to use the highest Bandwidth on the market
  4. 4. DESIGN AND IMPLEMENTATION PHASEThe Department is Data Center WG.1 ConglomerateServer Figure 2
  5. 5. References:Stair, R., & Reynolds, G. (2011). Principles of information systems. (10 ed.). Course Technology.Kay, R. (2002, May 14). Quickstudy: System development life cycle. Retrieved from http://www.computerworld.com/s/article/71151/System_Development_Life_Cyclehttp://www.google.com/search?q=network+structures&hl=en&rlz=1R2ITVB_enUS466&prmd=imvns&tbm =isch&tbo=u&source=univ&sa=X&ei=AG44T4PXAqPF0QGXnoDZAg&sqi=2&ved=0CEsQsAQ&b iw=1366bih=470

×