80 likes | 161 Views
IFS 231 Business Analysis. LECTURE 4 Technical Specification, Development, Testing and Roll-out. Contents. Difference between Functional – and Technical Spec Contents of Technical Specification Development User Acceptance Testing (UAT) Implementation Planning Roll-out and Training.
E N D
IFS 231Business Analysis LECTURE 4 Technical Specification, Development, Testing and Roll-out
Contents • Difference between Functional – and Technical Spec • Contents of Technical Specification • Development • User Acceptance Testing (UAT) • Implementation Planning • Roll-out and Training Business Analysis
Functional vs Technical Spec • A functional specification describes how a product will work entirely from the user's perspective. It doesn't care how the thing is implemented. It talks about features. It specifies screens, menus, dialogs, and so on. • A technical specification describes the internal implementation (the “how-to”) of the program. It talks about data structures, relational database models, choice of programming languages and tools, algorithms, etc. Business Analysis
Contents of Technical Spec • Introduction • System Overview • Design Considerations • Assumptions and Dependencies • General Constraints • Goals and Guidelines • Development Methods • Architectural Strategies • System Architecture • Policies and Tactics • Detailed System Design • Glossary • Bibliography Business Analysis
Development • Technical Spec should answer all questions by developers • The Software Release Life Cycle • Internal Testing • Debugging • Version Control Business Analysis
User Acceptance Testing (UAT) • BA should work out Test Plan • Functional Testing • Regression / Verification Testing • Automated and Stress Testing • Possibly do Manual now • Test Plan must be signed off Business Analysis
Implementation Planning • Hand Holding and Support • Back-out Plan? • Change Management • Transfer of Ownership to users & managers Business Analysis
Roll-out and Training • Big Bang Approach • Parallel Running • Phased Implementation • Training • Have manual available (or digital) • Sign-off • Post Implementation Review Business Analysis