Observations 2 1 1-to-one Interviews
12 Pages2191 Words172 Views
USC Sunshine Coast
Introduction to Systems Design (ICT115)
Added on 2020-03-04
About This Document
ICT115 - In this report, we discuss about System Design in this we have covered; Use of requirements gathering tools, Brainstorming techniques, and Prototyping. Some important questions related to the topic which was covered in this assignment.
Observations 2 1 1-to-one Interviews
USC Sunshine Coast
Introduction to Systems Design (ICT115)
Added on 2020-03-04
ShareRelated Documents
INTRODUCTION TO SYSTEM DESIGNSTUDENT NAMESTUDENT ID[Year]
ContentsQuestion 1...................................................................................................................................................21.1 One-to-one interviews.......................................................................................................................21.2 Workshop..........................................................................................................................................21.3 Use of requirements gathering tools.................................................................................................21.4 Brainstorming....................................................................................................................................21.5 Current system documentation.........................................................................................................21.6 Questionnaires..................................................................................................................................21.7 Observation.......................................................................................................................................21.9 Prototyping........................................................................................................................................32 Question 2................................................................................................................................................32.1 Use case diagram...............................................................................................................................32.2 Use case list.......................................................................................................................................42.3 Travel Swipe card transaction system................................................................................................42.3.1 UC-1............................................................................................................................................42.3.3 UC-3............................................................................................................................................52.3.4 UC-4............................................................................................................................................63 Question 3................................................................................................................................................73.2 use case list........................................................................................................................................83.3 charge fare sub system......................................................................................................................83.3.1 UC-1............................................................................................................................................83.3.2 UC-2............................................................................................................................................93.3.3 UC-3..........................................................................................................................................103.3.4 UC-4..........................................................................................................................................114 references...............................................................................................................................................11
Question 1To obtain information necessary for the development of the use case model, the following types of requirements gathering techniques can be used.1.1 One-to-one interviewsThis type of technique of requirements gathering involves arranging a one-to-one interview or meeting with the relevant stakeholders involved with the system. The meeting is between the system analyst and one stakeholder at a time. For example the interview can be with the prospective customer where by the system analyst will interview the customer to get user stories from the customer.1.2 WorkshopThe workshop technique is a method of requirements gathering where by the relevant stakeholders hold a workshop to determine the requirements of the proposed system. This technique can obtain a lotof information if preparation before the workshop is done by all stakeholders before the workshop.1.3 Use of requirements gathering toolsUse of requirements gathering tools for example Axia’s RFI/RFP templates which comprise a huge list of potential requirement and all stakeholders are given the template to choose the requirements they see fit the proposed system. The templates are split into different modules so that each stakeholder is given the module that is relevant to them.1.4 BrainstormingBrainstorming technique of requirements gathering can be done either individually or in groups with all stakeholders. While brainstorming ideas are collected. These ideas are then analyzed to come up with the requirements of the proposed system1.5 Current system documentationIF there is a current system in use, its documentation can be analyzed to come up with the requirementsfor the proposed system. The documentation of the existing system could include software vendor manuals and user manuals.1.6 QuestionnairesQuestionnaires method of requirements gathering is somehow similar to interviews but the questions asked to gather requirements are phrased as questionnaires which are given to all stakeholders. The questionnaires can be in form of a printed physical document, verbal questionnaire or even a web basedform designed as a questionnaire. The questionnaires answered are then analyzed to come up with the requirements which are used to come up with the use case diagram.1.7 ObservationObservation is a method of requirements gathering where by a system analyst observes how operations are done for the existing system and then draws requirements from the observation analysis. Observation can involve doing the work yourself as a system analyst to understand exactly how the current system is working.
1.9 PrototypingPrototyping is a method of requirements gathering where by requirements are collected and a prototype is created. The prototype is then used by the stakeholders so that they can get a feel of what the new system will be like. This will help them to understand what they actually need the new system to do thus they are able to provide better requirements (Seymour and Biemer, 2011).2 Question 2The diagram below shows the use case diagram representing the required functionality of the system.2.1 Use case diagram
End of preview
Want to access all the pages? Upload your documents or become a member.
Related Documents
Top 5 Requirements Elicitation Techniqueslg...
|4
|660
|206
System Analysis and Designlg...
|11
|1617
|281
System Analysis and Design: Techniques for Information Gathering and Process Analysislg...
|9
|1353
|390
Requirements Gathering Techniques and Stageslg...
|12
|1455
|76
Requirements Elicitation Techniques and Strategies for Common Campus Systemlg...
|14
|2240
|255
Introduction to Systems Design: A Case Study of Scene Brokerslg...
|13
|2133
|337