Systems Development/Project Management and Outsourcing

Topics: Software development methodology, Rapid application development, Project management Pages: 5 (1438 words) Published: June 13, 2013
The purpose of this assignment is engage in a discussion regarding Systems Development, Project Management, and Outsourcing. The seven phases of the systems development life cycle will be described. Relationships between the systems development life cycle and software development methodologies will be detailed. The phases in the SDLC, including activities associated with planning, analysis, design, development, testing, implementation, and maintenance, will be reviewed. The characteristics of a well-defined project plan will be listed and described. Project manager strategies, specifically those that can be used to ensure a successful project, will be summarized. Lastly, three primary outsourcing options will be identified with the advantages and disadvantages of each explained.   Business Driven Information Systems, Chapters 11 & 12 Questions Systems Development/Project Management and Outsourcing

The Seven Phases of the Systems Development Life Cycle, and Associated Activities

The Systems Development Life Cycle (SLC) is a methodology used to describe the process for building information systems, intended to develop information systems in a very deliberate, structured and methodical way, reiterating each stage of the life cycle. The SDLC process is used by systems analysts to develop information systems, including requirements, validation, training, and user ownership. According to Elliott & Strachan & Radford (2004), the SDLC "originated in the 1960s,to develop large scale functional business systems in an age of large scale business conglomerates. Information systems activities revolved around heavy data processing and number crunching routines". Systems Development Life Cycles can be broken down into seven phases. Phase One is the Planning Phase. The planning phase establishes a high-level view of the intended project and determines its goals. Phase Two is the Analysis Phase. The analysis phase defines project goals into defined functions and operation of the intended application, and analyzes end-user information needs. Business requirements are usually defined during this phase. Phase Three is the Design Phase. The design phase outlines the desired features and operations in detail, including screen layouts, business rules, process diagrams, code requirments including pseudo code, and other documentation. Phase Four is the Development Phrase. The development phase is where the actual code for the system is written. It takes all the design information from the previous phase and transforms it into an actual system. Phrase Five is the Testing Phase. The testing phase is where all the pieces of the system are brought together into a special testing environment, and checked for errors, bugs and interoperability. Segments of code that fail testing are referred back to phase four for further development to satisfy the operability requirements. Phase Six is the Implementation Phase. This is where the system is actually put into production and users begin real world utilization of the system. Phase six is actually the last step in overall development, since the software at this point is put into production, and running actual business (Cummings, 2006). Phase Seven is the Maintenance Phase. The Maintenance Phase is where performance changes, additions, corrections, and upgrade modifications are performed. Essentially, this is what happens during the rest of the software's life. This is by far the least glamorous, but is perhaps the most important step, in the life cycle of a system (Blanchard & Fabrycky, 2006).

Systems Development Life Cycle vs. Software Development Methodologies Where the Systems Development Life Cycle is a methodology used to describe the process for building information systems, a software development methodology is a framework that is used to structure, plan, and control the process of developing an information system. In simpler terms, a software development...

References: Blanchard, B. S., & Fabrycky, W. J.(2006) Systems engineering and analysis (4th ed.) New Jersey: Prentice Hall.
Cummings, Haag (2006). Management Information Systems for the Information Age. Toronto, McGraw-Hill Ryerson.
Elliott, G., & Strachan, J., (2004) Global Business Information Technology, Pearson Education.
Engardio, P. & Arndt, M. & Foust, D. (2006) The Future Of Outsourcing, Business Week, Nov 8, 2006.
Loucopoulos, P. & Karakostas, V. (1995). System Requirements Engineering. McGraw-Hill.
Continue Reading

Please join StudyMode to read the full document

You May Also Find These Documents Helpful

  • blood bank management system Essay
  • Effective and Efficient Project Management Essay
  • Project Management Essay
  • project management Essay
  • Project Management Essay
  • project management Essay
  • Management System Essay
  • project management Essay

Become a StudyMode Member

Sign Up - It's Free