1. Who uses the system? Users menus and control

2. User catalog List of all job titles of people thought to be likely on-line users of the system, giving job activities description. e.g. in a ticket issuing and revenue system for a public transport system, the user catalogue will include bus drivers and shop assistants.

3. Joe’s Yard User Catalogue Joe may be working in the shop or in the yard. He also compiles the restocking order. Fred works as a foreman in the yard from Tuesday to Friday. Mick works as a foreman in the yard from Saturday to Monday. Robbie works behind the counter in Joe’s.

4. Functional requirement definition Describe requirement Who requires it? Why is it required? How important is it? How is it measured? What target level is acceptable? Is it forward looking?

5. Joe’s Yard new Requirements(1) We want Joe to have a stock level on his stock, so that we know what needs to be ordered Joe requires it It is vital to the survival of his business Test to see if stock levels can be viewed and if a warning can be issued to when stock goes low Two extra pieces of information are required – a current stock level and a reorder level. It is forward looking.

6. Joe’s Yard new Requirements(2) We want Joe to know who his customers are, so that he can tout for repeat business. Joe requires it It is a venture into marketing Test to see if customer records are being kept for 2 years after their last purchase. An extra entity is required to hold customer information and we need to hold docket information for 2 years. It is forward looking.

7. Joe’s Yard new Requirements(3) We want Joe to be able to lodge requested items, so that he can make a decision on whether to stock them in the future or so that he can order them on demand. Joe requires it It is intended to provide a better level of service to his clients. Test to see if requested stock comes up on the supply order, where there is no corresponding stock in the system. Need to record stock requests and the customers who requested them. It is forward looking, but may cause difficulties if the stock item specification is incorrect or not easy to get. It may not be cost-effective.

8. Production of User roles Review user catalogue, picking out shared roles. –Roles can also be combined if the users deal with the same external entity, or have similar job titles or descriptions. Make out a list under the headings User role, job title, activities. –The user role of ticket issuer, for example, would be filled by users bus driver and shop assistant.

9. Joe’s User Roles Shop assistant (Joe, Robbie) –takes in the orders and payment. And decrements the stock level for the stock items ordered. –Takes in requests for stock to be ordered in. Foreman (Fred, Mick) –takes in the stamped order and issues the goods. –Takes in new supplies and increments the stock levels for the stock items ordered. Any requests are marked as awaiting collection.

10. Joe’s User Roles Managing Director (Joe) –Produce Financial Report –Produce order list using stock levels, requests and his own ideas –Mails current customers with ads? –Do all the things that the Shop Assistant and the Foreman do.

11. Function Definitions Function - A grouping of facilities or services required by the user. Data flow + processes -> Function Functions must be combined to give meaningful groupings in the system. Grouping criteria can be - –transactions --> transaction groups –parts of data model --> entity groups –perception of required services - SSADM Identify and agree the scope of the set of required functions

12. Identify the functions User initiated functions - examine DFDs, taking inputs from external entities. Identify resultant processes. System initiated functions - Using the DFM, identify processes which are not driven by flows from external entities Enquiry Functions - Check Requirements catalogue for Enquiry Functions and User initiated update functions.

13. Check the user's point of view Are groupings the right size? Split or merge as necessary. If merging, all merged events should –share the same set of external entities –occur at the same time –affect the same parts of the data model Presentation and sequence may be customised for each user role through Menu and Command structures. Other functions may emerge from Entity-event modelling

14. Identify the I/O structure Using the DFM, I/O Descriptions and Enquiry functions and user discussions If a function has several data flows –merge the on-line elements into a single I/O Structure, marking input or output in round brackets and pairing inputs and outputs –off-line elements have separate Input Structures and output structures

15. Logical Groupings of Dialogue Elements When all I/O structures have been made out, the dialogue elements are grouped, generally by user role, in such a way that the user role can access the different dialogues in the most convenient way. This is aided by making out a table of each dialogue and when and how often it is accessed (Dialogue Control Table). This prevents dialogues being presented in a way that is inconvenient to the user.

16. Menu and command structures There may be one menu structure per user-role. They will emerge from the Logical grouping of dialogue elements, with consultation with the users. It is a menu or hierarchy of menus which allows the user-role to access all its functions. Command structures allow for alternatives to returning to the initiating menu i.e. jumping to other dialogues.

17. Video Available Tape Detail Issue result Action confirmation (input) Borrow detail Issue confirmation (output) Issue cancellation (output) Borrower- name (output) Borrower-no. (input) Title (output) Tape-no (input) Sample I/O structure