CS2123, Introduction to Object Oriented Paradigm

Vision + Supplementary Specification

Wednesday, 29th September, 2004

Vision + Supplementary Specification

Purpose of following examples is not to write exhaustive Vision, Supplementary Specification and Glossary, rather Our objective is to learn core skills in Object Design, Use case Requirements, and Object Oriented Analysis

Supplementary Specification
Use cases are not sufficient Other kind of requirements that have requirements
Documentation Supportability Licensing Business rules etc.

Vision
The vision defines the stakeholders view of the product to be developed, specified in terms of stakeholders key needs and features. Containing an outline of the envisioned core requirements, it provides the contractual basis for the more detailed technical requirements [RUP] Why this system? Who are stakeholders? What are their needs? etc.
4

Supplementary Specification

Revision History Introduction Introduction of the document Functionality Logging and Error Handling Log all errors to persistent storage Security All users requires user authentication Usability Human Factors Text should be visible from 1 meter Avoid colors associated with common forms of color blindness Reliability Recoverability If failure to use external services ( payment authorize, accounting system ..) try to solve with a local solution (e.g. store and forward)

Supplementary Specification
Performance
Achieve authorization in less than 1 minute

Supportability
Adaptability Different customers have unique business rules and processing needs so same rule should be enabled Configurability configuration for different customers e.g. thick versus thin clients, two-tier versus N-tier

Implementation constraints
NextGen leadership insists on a java technologies solution,

Interfaces
Hardware and Interfaces Touch screen monitor, Barcode laser scanner, receipt printer, credit card reader etc.
6

Supplementary Specification
Domain (Business Rules)
How a domain or business may operate Company Policies, Government Laws, Rules are not requirements, they describe the constraints and how the domain works

Legal Issues
Licensing restrictions on open source components

Information in Domains of Interest

Some explanation of domains related to new software system To provide deeper insight to development team For example, Universal Product Code (UPC), European Article Number (EAN), Stock Keeping Units (SKU) and bar code symbology
7

Vision
Revision History Introduction Positioning Business Opportunity Problem Statement Stakeholders Description Key high level goals and Problems of stakeholders User level goals The users need a system to fulfill these goals Cashier: process sales, handle returns, cash in, cash out System Administrator: manage users, mange security Manager: start up, shut down
8

Vision

Product Overview Summary of benefits Summary of System features

Sales capture, payment authorization, system administration for users, security

Other Requirements and constraints

Design constraints, usability, reliability, performance, supportability, documentation etc.

Glossary
Noteworthy terms and their definitions Unclear and ambiguous terms Glossary table
Term Definition and information Aliases

Glossary as Data Dictionary Metadata (data about data) The glossary expands over time Term attributes Aliases, description, format (type, length), range of values, validation rules and relationship to other elements Composite Terms Like
Sale (includes other elements such as date location) Payment authorization request (a nickname for an aggregate of data and needs to be explained in the Glossary)
10