<Company Name>

System Name Stakeholder Requests

Version <1.0>
[Note: The following template is provided for use with the Rational Unified Process. Text enclosed in square brackets and displayed in blue italics (style=InfoBlue) is included to provide guidance to the author and should be deleted before publishing the document. A paragraph entered following this style will automatically be set to normal (style=Body Text).] [To customize automatic fields (which display a gray background when selected), select File>Properties and replace the Title, Subject and Company fields with the appropriate information for this document. After closing the dialog, automatic fields may be updated throughout the document by selecting Edit>Select All (or Ctrl-A) and pressing F9, or simply click on the field and press F9. This must be done separately for Headers and Footers. Alt-F9 will toggle between displaying the field names and the field contents. See Word help for more information on working with fields.]

System Name Stakeholder Requests Stakeholder.docx

Version: <1.0> Date: <13/4/2010>

Revision History
Date <13/04/2010> Version <1.0> Description <Introduction, Purpose, Problem, Analyst Summary, Assessing Reliability, Opportunity & Environment> <Adding Description about STRQ Profiles , & Scenarios> <Adding a stakeholder profiles> Author <Arfandi Deni>

<17/04/2010> <18/04/2010>

<1.1> <1.1>

<Arfandi Deni> <Arfandi Deni>

Confidential

<Company Name>, 2000

ii

System Name Stakeholder Requests Stakeholder.docx

Version: <1.0> Date: <13/4/2010>

Table of Contents
1. Introduction 1.1 1.2 1.3 1.4 1.5 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. Purpose Scope Definitions, Acronyms and Abbreviations References Overview 1 1 1 1 2 2 2 Error! Bookmark not defined. 3 3 3 3 4 4 4 4

Establish Stakeholder or User Profile Assessing the Problem Understanding the User Environment Recap for Understanding Analysts Inputs on Stakeholders Problem (validate or invalidate assumptions) Assessing Your Solution (if applicable) Assessing the Opportunity Assessing Reliability, Performance and Support Needs Wrap-Up Analysts Summary

Confidential

<Company Name>, 2000

iii

System Name Stakeholder Requests Stakeholder.docx

Version: <1.0> Date: <13/4/2010>

Stakeholder Requests
1. Introduction
[Write the introduction, the text below is introduction, background (blue font color)] Public transportation product line is software that will embody the same basic concepts, yet each city may have its own special needs. This topic has been proposed on score project, Explore developing a product line model that can be used to automatically generate systems that meet the specific needs of each city. This system is providing similar as ATM, but, the function is guide people that want to someplace by using public transportation guide by the system. This system is efficient to implement with the city that have lot of public transport & since each public transport have its own route & scheduling , most of citizen/passenger have difficulty in adjust their schedule, & most of public transport in the developing countries have unpredictable scheduling 1.1 Purpose The purpose of this document is to explain detailed information about the stakeholder request & to examine how will the stakeholder involve with the system. [Write the purposes, the text below is purposes (blue font color)] The product line system will be instantiated for any public transportation system such as busses, taxis, trains etc. The project includes requirements solicitation, requirements specification, design and the implementation. the final deliverable of this system is a kiosk in every public places that works similar to Automatic Teller Machine (ATM). Different people will be interact with this system , since the stakeholder in this system is the government , driver .The driver role in the stakeholder is represents as the public transport driver that has role in see scheduling , & report if any inconvenience condition if the system is not working as it should be or when there is any technical disturbance. The government is just being affected by the system This system is supposed to using Umple programming language, since the Umple language is still not well known, well be using php & java language

1.2 Scope [Write scope of scenarions, the text below is sample of scope (blue font color)] Document of Requirements Management Plan is consist with the prerequisite of the Building a Public Transportation System Product Line in city that might required this system The program has several scopes of scenarios when the program is activated 1. Administration The system administrator is the one who is responsible in the Managing Scheduling&Timetable , Handle the system if an internal problem occurred , example if there is a new scheduling for holiday , the system administrator is re-arrange the timeschedulling of the system from the usual scenario day , or when an accident is occurred , the administrator is re-arrange the routes 2. Operator

Confidential

<Company Name>, 2000

System Name Stakeholder Requests Stakeholder.docx

Version: <1.0> Date: <13/4/2010>

Operator is the one who is responsible in supervise how will the scheduling management on each branch of the area , &manage the passenger assistance , like if any accidence is occurred on the road , the operator will be informed by the driver who has been informed by the driver for assigning a passenger assistance to the passenger/citizen 3. Driver Driver is the one who is responsible to drive the public transportation (train, bus, etc), report if any occurrence is happened at the road, example if an accident is occurred, and the driver inform the operator for operator scenarios about whats the things must do for handle the situation?

4.

Passenger Passenger is the one who will use the system , also they give feedback & requesting passenger assistance , example : if the passenger is requesting assistance , the passenger will be assisted by the system that integrated on each public place

5.

Government Government is the one who will describe how the system will be & required on each city, the government will be affected by the system if the system is not initialized as its should be

1.3 Definitions, Acronyms and Abbreviations [Write any definitions, acronyms and abbreviation related on your system]

1.4 References

1.5 Overview The overview is explain about specified stakeholder roles description from the system , since the each city has their own requirement , this generalized scenario is cover about each specific role & deliverable to the system .

2. Establish Stakeholder or User Profile

Name: Job Title: What are your key responsibilities? What deliverables do you produce? Timetable How is success measured? Which problems interfere with your success? Which, if any, trends make your job easier or harder? For whom? Company / Industry:

Confidential

<Company Name>, 2000

System Name Stakeholder Requests Stakeholder.docx

Version: <1.0> Date: <13/4/2010>

3. Understanding the Work Environment (Observation)

Who are the users? What is their educational background? What is their computer background? Are users experienced with this type of application? Which platforms are in use? What are your plans for future platforms?. Which additional applications do you use that we need to interface with? What are your expectations for usability of the product? What are your expectations for training time? What kinds of hard copy and on-line documentation do you need?

4. Interview Scenario
Built your interview scenario (min. 5 specific question for each stakeholders)

5. Questionnaires
Built your questionnaires (min. 5 specific question for each stakeholders)

6. Analysts Inputs on Stakeholders Problem (validate or invalidate assumptions)

[If not addressed] Which, if any, problems are associated with: [List any needs or additional problems you think should concern the stakeholder or user]

Ask for each suggested problem: Is this a real problem? What are the reasons for this problem? How do you currently solve the problem? How would you like to solve the problem? How would you rank solving these problems in comparison to others youve mentioned?

7. Assessing Your Solution (if applicable)

What if you could... [summarize the key capabilities of your proposed solution] How would you rank the importance of these?

Confidential

<Company Name>, 2000

System Name Stakeholder Requests Stakeholder.docx

Version: <1.0> Date: <13/4/2010>

8. Assessing the Opportunity

Who needs this application in your organization? How many of these types of users would use the application? How would you value a successful solution?

9. Assessing Reliability, Performance and Support Needs

What are your expectations for reliability? What are your expectations for performance? Will you support the product, or will others support it? Do you have special needs for support? What about maintenance and service access? What are the security requirements? What are the installation and configuration requirements? What are the special licensing requirements? How will the software will be distributed? What are the labeling and packaging requirements? Which, if any regulatory or environmental requirements or standards must be supported? Can you think of any other requirements we should know about?

Other Requirements

10. Wrap-Up
Are there any other questions I should be asking you? If I need to ask follow up questions, may I give you a call? Would you be willing to participate in a requirements review?

11. Analysts Summary

[Summarize below the three or four highest priority problems for this user/stakeholder]

Confidential

<Company Name>, 2000