Prototyping
Prototyping is the most useful, especially when designing an information systems end-user interface. Consequently, it helps when there is some uncertainty on the requirements solutions. In a company, they can gather the information that will help them build an initial version of a solution by use of the prototype. Primarily by showing that to a customer then this can change the application and cycle around with the client again. Consequently, this repetitive process continues until the product meets the critical mass of business needs or for an agreed number of iterations. A prototype helps to encourage intense end-user participation in the development of the system as well as producing systems which meet the user’s requirements (Eid, 2015). However, by use of prototype technique in Walgreen when approaching investors, the company’s may be taken seriously because prototype will differentiate an idea from that one of a sketch from a computer-generated image. Nevertheless in the concept of a new product, using prototype technique will open other fabrication methods that were not known before which is so beneficial the questions that stem from the answers provided.at just an initial idea.
Interview
The interview can be used to gather information and can help to collect information for a company. However, it offers an opportunity to evaluate the validity of the information gathered. The interview is an effective technique for eliciting information on the complex subject making it easy to discover the big issues in the company by seeking opinions from the interview again many people like the concept. Notably, through the interview, the committee gathers facts which enables them to base their decisions on whether they will continue further with their suggestions. During the interview, the interviewee helps to give long and detailed answers which help the interviewer to respond and ask. The interview is a valuable time where a company explore human-computer interaction and to know how it is important to support individual tasks where the relationship is set for individual who is probably new to the company (Eid, 2015). Through the interview, one should build trust but at the same time control must be maintained during the interview to sell the system to provide the needed information.
Interface analysis
Interface analysis help to determine the requirements for compatibility and also disclosing the interfacing stakeholders early in the system. To gain insight into interface requirements, one should first review the current system and build a context diagram to show at a glance which entities send and receive data from it at a high level. However, the context diagram is divided into data flow diagrams for more analysis. Interface analysis shows how people interact with one another in the system and helps to discover the requirements which are needed to combine software into its new environment (Eid, 2015). Interface analysis helps in sizing and estimation. In the sizing concept, the interface is considered as a non-functional requirement. In the interface analysis, the expectations of the user are documented. Nevertheless, it helps to clarify the boundaries of the interacting application as well as identifying the functionality input and outputs of each interface. Also, interface analysis technique can be used to identify hardware interfaces with the software application.
Document analysis
Document analysis allows a company to confirm and cross-check the project requirement information by looking at the current documentation and other applicable information. Document analysis allows is set in a point that it is assumed that the existing documentation is easy to get. However, secondary sources of information make a company analyst gather more information about the existing solutions and also the analyst sees whether they have components which can be used in changing for the new solutions. Consequently, document analysis can be used to the company’s domain to solve problems without using the stakeholders time so it is a great way to gain information by asking the right questions (Reed, 2012). Document analysis is particularly valuable when replacing the systems with new ones which will provide higher functionality. It describes the act of reviewing the current documentations of comparable company processes or systems to gain pieces of information that are applicable in the company so the company’s projects should be highly considered.