1. Traditional SDLC Analysis
Work Group 1: Mohammed Kamil Zakari, Eric Odame, Jay White, Ajiboye Johnson
With the rapid increase in availability and use of information systems and software among large
businesses, it became apparent that a standard was needed to systematically and methodically
develop systems for the enterprise. The approach that was developed was called the traditional
System Development Life-Cycle (SDLC.) The traditional SDLC incorporated several linear
steps to help maintain a methodical and systematic approach to the development of information
systems. The steps included are; feasibility study, requirement/system analysis, system design,
system development, system implementation, system testing, and maintenance. The SDLC
begins with the feasibility study, in which the project is defined with high-level objectives, and
an initial set of goals is determined. With the project defined the SDLC moves into the
requirement analysis. This is where information is gathered to help better define the goals and
needs of the project. The end-user is a vital component of this step, as it is here that their needs
are defined and documented. Once the user’s needs have been defined, the system can be
designed. This process will include details about the system, diagrams detailing the system, and
even pseudo code that may be used in the development of the system. The system is then
developed to ensure that everything is functioning according to the goals and requirements that
were established early on in the process. If everything is functioning properly it is time to
implement and then test the system. The maintenance of the system is where the system will
remain for the rest of its lifecycle, and can include changes and upgrades to the system. The
traditional SDLC focuses on strict management of the project with target dates, budgets, and the
implementation of the system tightly controlled and followed. This type of SDLC is best used in

2. situations where the system can be well identified up front and when the management does not
have a lot of experience with developing a system. This type of SDLC also works very well
when implementing a newer version of a system that is already in use, or when quality is more
important than time and budget.
Pros Cons
The amount of documentation required helps The excessive documentation can cause delays
to 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 be
helps 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, the
used 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 cause
identified from the beginning. rigidity in the process, restricting flexibility.
Figure 1

3. WG 1 “The Department”
“Data Center”
Our department used to be the data center of the ABC Associates for several years off-site and
we have been bought over to WG.1 Conglomerate. We are still going to be off-site but we are in
the 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. DESIGN AND IMPLEMENTATION PHASE
The Department is Data Center
WG.1 Conglomerate
Server
Figure 2

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_Cycle
http://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