This is my school homework, Slides of History

Download This is my school homework and more Slides History in PDF only on Docsity!

Moving into

Implementation

CORRESPONDING TO CHAPTER 12 OF “SYSTEMS ANALYSIS

AND DESIGN,” BY DENNIS, WIXOM, AND ROTH

Learning Objectives

Understand what happens during the implementation phase.

Be familiar with practices for managing the programming process.

Explain different types of software testing techniques.

Describe best practices for developing user documentation.

People involved in implementation

Project manager needs to carefully manage the

implementation process, as with other stages of the

process.

Analyst often is not the one to program, install, or

customize the system (at least in large organizations), but

the analyst’s work is not done!

Analysts help with testing and documentation

Programmers or other technical specialists

Quality assurance professionals (in large organizations)

Managing the

Programming Process

PROJECT MANAGEMENT DURING CONSTRUCTION

Coordinating Activities



Weekly (hopefully brief) meetings



Create and follow standards



Organize programmers’ work areas

o Development area

o Testing area

o Production area

Coordinating Activities, cont’d



Implement change control mechanisms



Use program log to monitor program changes

See also https://en.wikipedia.org/wiki/Distributed_version_control

See also https://www.visualstudio.com/products/visual-studio-team-services-vs

Testing

ENSURING THE SYSTEM FULFILLS REQUIREMENTS

Testing Philosophy



Testing helps ensure that the system performs as outlined in

the specifications.



It is unwise to test spontaneously without an overall testing

plan



Testing must be done systematically and results documented

carefully

11

Image from http://savvycomsoftware.com/functional-testing-a-critical-

process-of-software-testing/

Categories of Testing

Unit testing

o Tests each module – Does it performs its function?

Integration testing

o Tests the interaction of modules - do they work together?

System testing

o Tests to assure that the software works well as part of the overall system,

including nonfunctional requirements

Acceptance testing

o Tests to assure that the system serves organizational needs

Unit Testing



Black Box Testing

o Focuses on whether the unit meets requirements stated in

specification



White-Box Testing

o Looks inside the module at actual code

Important terms/tools for unit testing



Stubs: placeholders for modules to enable the

modules around them to be tested



Hardcoded values: placeholder values placed into

the system during testing when calculation of those

values has not yet been coded

Integration Testing



User interface testing

o Tests each interface function



Use-scenario testing

o Ensures that each use scenario works correctly



Data flow testing

o Tests each process in a step-by-step fashion



System interface testing

o Ensures data transfer between systems

Acceptance Testing



Alpha Testing

o Performed by users to assure they accept the system; frequently repeats

earlier tests



Beta Testing

o Uses real data, not test data. Actual users monitor for errors or needed

improvements.

 User sign-off following Acceptance Testing indicates the

system is ready to be placed into production.

Acceptance Testing