ПОСТАНОВКА ЗАДАЧИ
Задача следующая -
Необходимо подготовить документ Use Case, включащий в себя описание операций, производимых над Заказом на покупку (Purchase Order). Озаглавим его "Maintain Purchase Order".
Условия следующие:
- Документ должен максимально использовать предложенные материалы (в рамках данного Use Case)
- Формат и структура документа определяются самостоятельно. От Вас ожидается формат, который, по Вашему мнению, наилучшим образом подходит для документов Use Case Specification.
- Описанные в Use case действия должны отражать наиболее удобные для пользователя сценарии, исходя из Вашего опыта работы в качестве аналитика.
- Документ должен быть подготовлен на английском языке.
Время выполнения задания - 1 рабочий день
ИСХОДНАЯ ИНФОРМАЦИЯ
Payroll System Glossary
Introduction
This document is used to define terminology specific to the problem domain, explaining terms, which may be unfamiliar to the reader of the use-case descriptions or other project documents. Often, this document can be used as an informal data dictionary, capturing data definitions so that use-case descriptions and other project documents can focus on what the system must do with the information.
Definitions
The glossary contains the working definitions for the key concepts in the Payroll System.
Bank System
Any bank(s) to which direct deposit transactions are sent.
Employee
A person that works for the company that owns and operates the payroll system (Acme, Inc.)
Payroll Administrator
The person responsible for maintaining employees and employee information in the system.
Project Management Database
The legacy database that contains all information regarding projects and charge numbers.
System Clock
The internal system clock that keeps track of time. The internal clock will automatically run the payroll at the appropriate times.
Pay Period
The amount of time over which an employee is paid.
Paycheck
A record of how much an employee was paid during a specified Pay Period.
Payment Method
How the employee is paid, either pick-up, mail, or direct deposit.
Timecard
A record of hours worked by the employee during a specified pay period.
Purchase Order
A record of a sale made by an employee.
Salaried Employee
An employee that receives a salary.
Commissioned Employee
An employee that receives a salary plus commissions.
Hourly Employee
An employee that is paid by the hour.
Problem Statement
As the head of Information Technology at Acme, Inc., you are tasked with building a new payroll system to replace the existing system which is hopelessly out of date. Acme needs a new system to allow employees to record time card information electronically and automatically generate paychecks based on the number of hours worked and total amount of sales (for commissioned employees).
The new system will be state of the art and will have a Windows-based desktop interface to allow employees to enter timecard information, enter purchase orders, change employee preferences (such as payment method), and create various reports. The system will run on individual employee desktops throughout the entire company. For reasons of security and auditing, employees can only access and edit their own time cards and purchase orders.
The system will retain information on all employees in the company (Acme currently has around 5,000 employees world-wide). The system must pay each employee the correct amount, on time, by the method that they specify (see possible payment methods described later). Acme, for cost reasons, does not want to replace one of their legacy databases, the Project Management Database, which contains all information regarding projects and charge numbers. The new system must work with the existing Project Management Database, which is a DB2 database running on an IBM mainframe. The Payroll System will access but not update information stored in the Project Management Database.
Some employees work by the hour and they are paid an hourly rate. They submit timecards that record the date and number of hours worked for a particular charge number. If someone works for more than 8 hours, Acme pays them 1.5 times their normal rate for those extra hours. Hourly workers are paid every Friday.
Some employees are paid a flat salary. Even though they are paid a flat salary, they submit timecards that record the date and hours worked. This is so the system can keep track of the hours worked against particular charge numbers. They are paid on the last working day of the month.
Some of the salaried employees also receive a commission based on their sales. They submit purchase orders that reflect the date and amount of the sale. The commission rate is determined for each employee, and is one of 10%, 15%, 25%, or 35%.
One of the most requested features of the new system is employee reporting. Employees will be able to query the system for number of hours worked, totals of all hours billed to a project (i.e., charge number), total pay received year-to-date, remaining vacation time, etc.
Employees can choose their method of payment. They can have their paychecks mailed to the postal address of their choice, or they can request direct deposit and have their paycheck deposited into a bank account of their choosing. The employee may also choose to pick their paychecks up at the office.
The Payroll Administrator maintains employee information. The Payroll Administrator is responsible for adding new employees, deleting employees and changing all employee information such as name, address, and payment classification (hourly, salaried, commissioned), as well as running administrative reports.
The payroll application will run automatically every Friday and on the last working day of the month. It will pay the appropriate employees on those days. The system will be told what date the employees are to be paid, so it will generate payments for records from the last time the employee was paid to the specified date. The new system is being designed so that the payroll will always be generated automatically and there will be no need for any manual intervention.
Payroll System Supplementary Specification
Objectives
The purpose of this document is to define requirements of the Payroll System. This Supplementary Specification lists the requirements that are not readily captured in the use cases of the use-case model. The Supplementary Specifications and the use-case model together capture a complete set of requirements on the system.
Scope
This Supplementary Specification applies to the Payroll System which will be developed by the OOAD students.
This specification defines the non-functional requirements of the system; such as reliability, usability, performance, and supportability as well as functional requirements that are common across a number of use cases. (The functional requirements are defined in the Use Case Specifications.).
References
Functionality
Usability
Reliability
The main system must be running 98% of the time. It is imperative that the system be up and running during the times the payroll is run (every Friday and the last working day of the month).
Performance
The system shall support up to 2000 simultaneous users against the central database at any given time, and up to 500 simultaneous users against the local servers at any one time.
Supportability
Security
The system should prevent employees from changing any timecards other than their own. Additionally, for security reasons, only the Payroll Administrator is allowed to change any employee information with the exception of the payment delivery method.
Design Constraints
The system shall integrate with an existing legacy system, the Project Management Database, which is a DB2 database running on an IBM mainframe.
The system shall interface with existing bank systems via an electronic transaction interface (NOTE: THE FORMAL INTERFACES WITH THE EXTERNAL BANK SYSTEM WOULD NEED TO BE DEFINED EARLY IN THE PROCESS AND DEFINED HERE OR IN A SEPARATE SUPPORTING DOCUMENT. SUCH A DEFINITION IS OUT OF THE SCOPE OF THIS COURSE). The system shall provide a Windows-based desktop inte
РЕШЕНИЕ
Project "Use Case Document with Maintain Purchase Order"
Goal
Make Use Case Document with Maintain Purchase Order Use Case.
Scope
Scope of project is Nikolay Priezhiy, Evgeny Igumnov, source documents.
Roles and stakeholders
| Role | Stakeholder |
| Project Manager | Evgeny Igumnov |
| Analyst | Evgeny Igumnov |
| Customer | Nikolay Priezhiy |
Stakeholders interests
| Stakeholder | Interest |
| Evgeny Igumnov | Build Use Case Document with Maintain Purchase Order in schedule |
| Nikolay Priezhiy | Get Use Case Document with Maintain Purchase Order in schedule |
Risk (Evgeny Igumnov opinion)
| Risk | Solution |
| Not enough information in source documents | Try to send email for request additional information |
| English language | Try to use dictionary ;) |
| Some task from Alekta Ltd | Not manage, But I can don’t have dinner and have 1 additional hour. :( |
Project Plane
Priority:
1 – High
Project estimation
Project process and artifacts
Domain Picture
Report
- 7:40-8:00 Readied source documents
- 8:00-8:30 Made Project Planning
- 8:30-9:00 Made Domain Picture
- 9:00-10:00 Made Use Case Diagram
- 10:00-10:40 Made Use Case Document
Use Cases
Actors
| Actors | |
| Employer | A person that works for the company that owns and operates the payroll system (Acme, Inc.) |
| Payroll Administrator | The person responsible for maintaining employees and employee information in the system. |
| Payroll System | Payroll System ;) |
...
Use Case Diagram
Enter Purchase Order
| Context of using | If customer want make order than employer must register purchase order in Payroll system |
| Actor | Employer |
| Before use case | Login in payroll system |
| Trigger | Customer want make order |
| Scenario |
|
| After use case |
Last working day of the month Payroll
| Context of using | Every month employers must receive salary |
| Actor | Payroll System |
| Before use case | |
| Trigger | Last working day of the month |
| Scenario |
|
| After use case |
Other use case...
Functional Requirements
| № | Requirement |
| 1 | Functional Requirements 1 |
| 2 | Functional Requirements 2 |
| 3 | ... |