Академический Документы
Профессиональный Документы
Культура Документы
Inception
Artifacts generated during Inception Artifact
Vision and Business Case Use-Case Model
Comment
Describes the high-level goals and constraints and provides an executive summary Describes the functional requirements of high-level goals, and related non-functional requirements Describes other requirements Begin keeping a dictionary of key domain terminology
Supplementary Spec.
Glossary
Iteration Plan
Inception
ATM Example: (Partial) Vision
Version Date Description Author
J. TenEyck
Inception Draft Jan. 15, 2008 First draft to be refined primarily during Elaboration
Stakeholder Descriptions
Participating Banks Want to make sure that access to their customer account information is safe and secure, transaction information is accurate and reliable, and that their own account card is readily recognizable at a large number of ATMs. Bank Customers Want easy, low-cost, remote access to their accounts, but want to be assured that their accounts are secure and not accessible to hackers or other third parties.
Consortium server must be able to identify the home bank of the customer card.
Customer
Use services
ATM Network
Actors
This table relates the goals, benefits and solutions at a higher level not solely related to use cases.
The Vision Document is also useful to the Technical people for beginning the process of determining and describing the requirements of the system. It indicates the important high-level and stakeholder goals that need elaboration in the use cases.
Note that the class project is a system taken out of any particular context. The problem statement will serve instead of a vision document, and the remainder of the inception process will proceed from there.
The Glossary
During Inception, the Glossary should be a simple listing of terms with brief descriptions or definitions. During Elaboration, the Glossary expands into the role of a Data Dictionary.
Term
ATM
Aliases
Automatic teller machine
It is important to start early in keeping a glossary of terms so that all members of the design team have the same concept of what each term means. In the example shown here, The term ATM refers to both the physical terminal and the supporting software that it contains.
The Glossary
In subsequent elaborations the Glossary is refined to include Format (type, length, unit) Relationship to other terms (attributes, associations, methods) Range of values Validation rules
Use Cases
During Inception some of the most important stakeholder goals should be developed as use cases.
During Inception, it is not necessary, nor necessarily desirable, to generate a fully dressed use case, nor is it necessary to develop any but the most important of the stakeholder goals into use cases.
Essential Use Case Statements
Name ATM Withdrawal
Brief Narrative
Preconditions Post-conditions
User must have a valid bank card, must indicate an amount < balance User obtains proper cash, user account correctly debited, transaction recorded at bank
Supplementary Specifications
The difference between the component features of the supplementary specification and the Vision is that the Supplementary Specification contains information more particular to the technical specialists whereas the Vision is a broader document that is most useful for management:. Components of the Supplementary Specification Document
Human Factors Reliability Performance Adaptability Configurability
Text visible from at least 1 meter. Clear, step-by-step instructions for use. The consortium computer must keep a transaction record for member banks to use for comparison Each transaction should require less than 1 minute of customers time Projected growth rate of the ATM base and member banks.
Will use an X.25 based intranet to connect ATMs and member banks with consortium computer Implementation Constraints Recommend a Linux based consortium server and java as the programming language for ATM client code. Interfaces Card reader in ATM. Touch screen monitor. Receipt printer.
Iteration Plan
Time frame for the iteration: Start date: Jan. 15, 2008 Deliverable Artifacts Use cases:
Access Account Deposit Withdraw Identify concepts within the ATM network to help develop an initial concept model diagram
Balance Statement
Identify boundary between system and identified actors Identify states and state transitions for each user initiated button event A simulation demonstrating the user interaction with an ATM terminal Develop and Execute a Plan to ensure that the various user events do not cause the system to enter an error state or to hangup.
Domain Model (Concept Model Diagram) State Diagram Software prototype Test Plan