INFS 6225 ObjectOriented Systems Analysis Design Chapter 12

INFS 6225 Object-Oriented Systems Analysis & Design Chapter 12: Construction

Construction • Activities needed to build the system: – Programming – Testing – Documentation • Programming – Job of the programmer – Can be largest component (time & cost) • Testing – Primary responsibility of Analysts during Construction Stage

Managing Programming • More programmers = longer build time (why? ) • Must have weekly project meetings to discuss changes • Create & follow standards • Keep effort well organized • Use Program Log • Work to avoid/minimize Scope Creep

Testing • 4 Stages of Tests: 1. Unit - focus on single unit (Class) 2. Integration - does set of Classes work together without error 3. System - do all Classes work together without error 4. Acceptance - confirm system is complete & meets business needs • alpha testing - use made-up data • beta testing - use real data Why should tests include nonsensical data?

Documentation • 2 Types of documentation: 1. System - help programmers & systems analysts understand & maintain system 2. User -help users understand & use system – Most users begin working with system w/o training & w/o reading user manual – 3 hours to write a page of documentation (2 hours per online screen) What are advantages to online documentation?

Types of Documentation • Reference Documents (Help System) - help user perform specific function • Procedures Manuals - how to perform business tasks • Tutorials - how to use major components of a system Topics should be written from user’s point of view

Navigation Terms • Commands in the user interface (Action & Object) • Major Concepts in the system • Business Tasks to be performed • Synonyms - e. g. , Quit or Exit