appliancewarehouse case study 9
kamishliang
appliancewarehousecase4_Kamishlian.docxRunning Head: QUESTIONER 1
Joseph Kamishlian
June 2020
Questionnaire 1 (Service Repair)
As Emily, the new service manager starts work, a new system for scheduling appliance repair has been proposed. In order for the company to get best results and optimal performance from employees, the organization has resorted to interview some employees to get their opinion on the proposed new system. A list of the employees to be interviewed include; service manager, workshop manager, parts manager, and repair technicians. Below are some of the important questions that these employees will be asked concerning the new proposed system.
Please click here to indicate your informed consent to participate in this study |_|
[Questionnaire: Service repair department]
In charge |
|
Department |
|
Results |
|
Organization |
|
Date | [Date] |
Period |
|
Please read and answer all questions
Are you happy with the current system?
[Type an answer here.]
[Type an answer here.]
[Type an answer here.]
What are some of the challenges that you face?
1. [Type an answer here.]
[Type an answer here.]
[Type an answer here.]
What is your opinion on the proposed new system?
1. [Type an answer here.]
[Type an answer here.]
[Type an answer here.]
In what ways do you think the new system will improve operations?
1. [Type an answer here.]
[Type an answer here.]
[Type an answer here.]
How is the new system likely to impact on your work?
1. [Type an answer here.]
[Type an answer here.]
[Type an answer here.]
What are some of the changes you would like to see under the new system?
1. [Type an answer here.]
[Type an answer here.]
[Type an answer here.]
Do you understand how the proposed system works?
1. [Type an answer here.]
[Type an answer here.]
[Type an answer here.]
Do you have any reservations about the new system?
1. [Type an answer here.]
[Type an answer here.]
[Type an answer here.]
Please indicate appropriately with either yes or no
Do you agree with the proposed new system?
Do you think the new system will help to increase sales?
Do you think that the proposed new system will improve efficiency?
Are willing to support the new system?
Do you have any additions you would add to the new system?
Questionnaire 2 (Appliance Warehouse)
The list of employees to be interviewed is as follows; warehouse manager, operations manager, project manager, and warehouse attendant. The type of technique chosen for this project is Rapid Application Development technique (RAD). This is because of the urgency of the matter. RAD was also chosen because we do not have to come up with individualized questions for each employee interviewed.
Please click here to indicate your informed consent to participate in this study |_|
[Appliance Warehouse Questionnaire]
In charge |
|
Department |
|
Results |
|
Organization |
|
Date | [Date] |
Period |
|
Please read and answer all questions
1. What areas of your work would you like to see some changes?
[Type an answer here.]
[Type an answer here.]
[Type an answer here.]
2. What do you think AW (Appliance Warehouse) is doing right?
1. [Type an answer here.]
[Type an answer here.]
[Type an answer here.]
3. What do you think AW is doing wrong?
1. [Type an answer here.]
[Type an answer here.]
[Type an answer here.]
4. What are your suggestions on how AW can increase capacity?
1. [Type an answer here.]
[Type an answer here.]
[Type an answer here.]
5. What is your opinion about procurement system at AW?
1. [Type an answer here.]
[Type an answer here.]
[Type an answer here.]
6. What changes do you believe can help to improve procurement system at AW?
1. [Type an answer here.]
[Type an answer here.]
[Type an answer here.]
7. Do you believe you are well equipped to handle your duties efficiently?
1. [Type an answer here.]
[Type an answer here.]
[Type an answer here.]
8. What kind of support would like to get from AW to facilitate your work?
1. [Type an answer here.]
[Type an answer here.]
[Type an answer here.]
Please indicate appropriately with either yes or no
9. Are you getting enough support from AW to do your work?
10. Are you happy with current system at AW?
11. Are you happy with your work?
13. Do you think AW can do better to increase sales?
14. Do you like working for AW?
Summary
· (1)gathering requirements,
· (2)representing requirements, and
· (3)validating and verifying requirements.
During requirements engineering, the business-related requirements for the new information system are identified. Scalability is considered to ensure that the system can support future growth and expansion. Security is an essential requirement of all modern connected systems. The TCO is also estimated to identify all costs, including indirect costs.
Popular team-based approaches include JAD, RAD, and agile methods. JAD is a popular, team-based approach to fact-finding and requirements engineering. JAD involves an interactive group of users, managers, and IT professionals who participate in requirements engineering and develop a greater commitment to the project and to their common goals.
RAD is a team-based technique that speeds up information systems development and produces a functioning information system. RAD is a complete methodology, with a four-phase life cycle that parallels the traditional SDLC phases.
Agile methods attempt to develop a system incrementally by building a series of prototypes and constantly adjusting them to user requirements. Tools are often avoided and replaced with simpler aids, such as whiteboards and sticky notes to facilitate communication.
The requirements gathering process includes interviewing, document review, observation, questionnaires, sampling, and research. Successful interviewing requires good planning and strong interpersonal and communication skills. The systems analyst must decide on the people to interview; set interview objectives; and prepare for, conduct, and analyze interviews. The analyst also might find it helpful to use one or more software tools during fact-finding.
Systems analysts use various tools and techniques to represent system requirements. Natural language, structured or unstructured, is still the default. Requirements can be stored as simple text in a plain file or in an Excel spreadsheet. They can also be stored online for automated search and analysis.
Diagrams are another way of representing requirements. They are suitable for analysts who are more visually oriented. They can also capture complementary aspects of the system requirements. Sample diagram types include FDDs, business process diagrams, and DFDs.
Models provide a more formal representation of system requirements. The UML is a widely used method of visualizing and documenting software design through the eyes of the business user. UML tools include use case diagrams and sequence diagrams to represent actors, their roles, and the sequence of transactions that occurs.
Systems analysts should carefully record and document factual information as it is collected, and various software tools can help an analyst visualize and describe an information system.
Requirements V&V is concerned with demonstrating that the requirements define the system that the customer really wants. Validation asks if the correct requirements are stated, while verification asks if the requirements are stated correctly.
All requirements engineering activities can be helped through the judicious use of tools. They provide automated support for requirements attributes such as traceability. For very large systems with thousands of requirements to manage, CASE tool assistance is necessary.
