Chapter 8 Review Questions Solutions 1.Describe the prototyping process of designing forms and reports. What deliverables are produced from this process? Are these deliverables the same for all types of system projects? Why or why not? Designing forms and reports is a user-focused activity that typically follows a prototyping approach. First, you must gain an understanding of the intended user and task objectives by collecting initial requirements during requirements determination. After collecting the initial requirements, you structure and refine this information into an initial prototype. Structuring and refining the requirements are completed independent from the users, although you may need to occasionally contact users to …show more content…
7.Provide some examples where variations in user, task, system, and environmental characteristics might impact the design of system forms and reports. User-related concerns include experience, skills, motivation, education, and personality. Task-related concerns include time pressure, cost of errors, and work duration. The system platform is a system-related concern, and lighting, sound, and task interruptions are environment-related concerns. 8.Describe the process of designing interfaces and dialogues. What deliverables are produced from this process? Are these deliverables the same for all types of system projects? Why or why not? The design process is a user-focused activity that typically follows a prototyping approach. First, you must gain an understanding of the intended user and task objectives by collecting initial requirements during requirements determination. After collecting the initial requirements, you structure and refine this information into an initial prototype. Structuring and refining the requirements are completed independent from the users, although you may need to occasionally contact users to clarify some issue overlooked during analysis. Finally, you ask users to review and evaluate the prototype. After reviewing the prototype, users either accept the design or request changes. If changes
Phase 2: Develop mock up application view based on user’s requirements. We mainly used HTML to design the mock up application interface for user to explore the outlook, process, and functions.
[List the user’s key responsibilities with regard to the system being developed— that is, captures details, produces reports, coordinates work, and so forth.]
Q1: Briefly explain designing requirements that’s are required when designing the hardware and software infrastructure:
4. (A) The ___________ approach to systems development has often been referred to as the "waterfall" model. a. SDLC b. prototyping c. RAD d. XP
Another way of successfully gathering information is by building a prototype or model of the system, so that users can test or get an idea of what the finished product will be like. With this they can determine issues, problems, or inconsistency with the system. Another important part of gathering information is organizing it so that it can be understood and put to proper use. I propose categorizing the requirements into functional requirements, operational requirements, technical requirements, and transitional requirements. The functional requirements define how the user thinks the system is functioning overall, the operational requirements define what background processes need to be executed in order for the system to work optimally over a period of time, the technical requirements define what technical issues that must be addressed in order to successfully implement the system, and the transitional requirements define the processes or steps needed to implement the system smoothly and successfully. ("Mind Tools", 2012).
The commonly used methods of observation, interviews, etc., can help analysts pinpoint exact requirements based on user input and business processes. According to Charvat (2003), “One of the biggest benefits of a proper user requirements specification is that you'll be able to plan and estimate your project correctly, decreasing the chance of cost and time overruns.” The analyst must listen to the employees and gain a thorough understanding of all business processes before establishing the new system requirements.
Q:1. Briefly explain following designing requirments that are required when designing the hardware and software infrastructure :
Which is requirements needed, after all the information the team will analyze to determine software requirements and generate a report. Then we move to the selection and design, this will occur when the team creates several designs and share with everyone on the project. We will identify any weakness, if we have any successful prototypes it should show how the software will operate. Implementation phase should proceed without any issues if there is any it must be correct during this time. A planned out schedule should allow for any unexpected incidents. When the implementation stage is complete we move to operation when our software has been designed and does what it was designed to do. We will do a review and evaluation which consist of performance, cost and
Design of develop – Once the user stores have been interpreted they are translated into either UI or template design by the development team. Quality Analysis – The prototype is subjected to the quality testing procedure that is mentioned in the above chapter to maintain design integrity. Client Review – This task is optional and can depend on the iteration.
Design is the starting phase in the improvement stage for any built product or application. The designer will likely deliver a model or of requirement and representation that will later can be used. Starting, once application necessity have been analyzed and broke down into three configurations like the three perspectives one is design, code and test these are the main things require to build a software application.
The current development process devotes a large amount of time at the front end of development to establishing customer needs and converting them into system level requirements. The client-site team meets with customers, learns their needs, develops specifications, verifies them with the customers, and then sends them offshore for development. This is a very formalized, documented process. (+)
Use this section to identify the design documents that have been developed and summarizes the overall solution design in a succinct statement. Also, define why each of these design documents is necessary for the project.
The interview session has been done by include an open-ended and closed-ended question which are related to the implemented project. Next, sampling technique is executed by system analyst who does evaluation to the current system or prototype. These processes give feedback in evaluation form that filled after tested the system. Lastly, observation is performed by using questionnaire form. According to Burch (1992), the questionnaire is analyzed and transform into structured form that easy to understand. After all information has been collected, structuring of system requirement takes place. It focused on development process modeling which perform “graphically representing the process, or actions, that capture, manipulate, store, and distribute data between a system and environment” (Hoffer, George, & Valacich, 2012, p. 182). In this step, Data flow diagram (DFD) is structured by system analyst using special tools and techniques to create a decision table. According to Hoffer, George and Valacich (2012), decision table is a “diagram of process logic where the logic is reasonably complicated” (p. 200). This table is useful to help system analyst to make a decision toward the project. Then all information’s gained from this phase are documented in System Analysis Report (SAR) that acts as a guideline or reference to the future system development project (Burch, 1992).
The requirements gathering and analysis phase is the most critical phase for the overall success of the project because this phase helps “identify and capture stakeholder requirements using customer interviews and surveys” (Smith, 2016). In order to successfully capture software requirements from the stakeholder, developers need to conduct conference meetings to understand the capabilities of the software. This conference meeting usually takes place only once, so it is essential that developers collect all the information required for the software during the elicitation requirement meeting. For developers to be successful in collecting all the required information, it is a