Requirements For Part Of A Ticket Issuing System

There are several techniques used in the documentation process. As a system analyst I would propose to the members of this group a straightforward standardized approach. A reasonable suggestion for this project would be to use the Procedure Manual technique for documenting this system. The Procedure Manuals will provide instructions on how to operate and understand how the system works. These manuals are also used as a guide that can be updated at different intervals for future users. Procedure Manuals are also made available to users via the Web. This new approach has made it convenient for users to seek support in a much faster way by offering a FAQ page, and online chat (Kendall & Kendall, 2011). In

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).

This way the IT department can understand what the higher level and lower level employees need for system stability and a better graphical interface. Another plan of action would include the method of Systems Development Life Cycle or SDLC. The phases of this method are planning, analysis, system design, implementation and operation. First we must plan on what exactly we are trying to accomplish. We know we need to upgrade the Riordan Manufacturing system. Next we must analyze the system and look for problematic errors. A project proposal can be essential to launching a system analysis (Farah, 2013). These are things to keep in mind: understand the business situation or problem, understand the significance to the problem in the organization, think of alternate solutions, the use of computer information systems for solutions, find people interested in the solving the problem (Farah, 2013). This plan is used to decrease redundancies, errors, and increase security. Finding all the weak spots in the company will help in the improvement of integrating an updated efficiently functioning system. Feasibility is important to account for when upgrading the system. Integrating a CRM will help to work with customers and understand their needs and wants to benefit the company and the relationship with their customers. Designing the system will involve knowing what kind of software is needed to store and

Functional requirements define the internal workings of the software: that is, the calculations, technical details, data manipulation and processing, and other specific functionality that shows how the use cases are to be satisfied. It also contains nonfunctional requirements, which impose constraints on the design or implementation (such as performance requirements, quality standards, or design constraints). Applied Software Project Management (2005)

The information system’s requirements in the systems planning phase are based on a case summary, potential interview questions, and the systems analyst’s experience in systems planning. One must not only generate requirements based specifically on what users’ state they want or need. Analysts must also generate requirements based on insight into the overall organization and project goals.

On the other hand, the quality characteristics which are must be maintained by the software are known as non-functional requirements. The functional requirements of the software are must be tested at the beginning phase but the security requirements, reliability and safety requirements (Non-functional requirements) are tested after the end of propose process.

Requirement Analysis: collect the business needs, document the requirements, and help team members to prepare Functional and enhancement Specification Document and Technical detail design document.

The non-functional requirements are the attributes of the system; these include: reliability, performance, cost, system quality attributes, and the challenges encountered during installation.

Non-functional requirements describe how the system operates and can also be limitations on the design of the system.

Hi Frederick, great job on setting all nonfunctional requirements with a unit of measurement. Nonfunctional requirements need to translate as clear as possible the user stories in measurable terms so that the developers are able to understand the supposed project to be delivered, creating this objectivity save time and effort and possible nonfunctional requirements misrepresentation.

After all the information is obtained, analysts will review, analyze and structure the information obtained so they can develop an overall understanding of the new system’s requirements. To define the new system requirements; drawing diagrams, workflow diagrams and activity diagrams will be used to express and model the new system’s processing requirements. Last, the IT team selects and recommends an alternative to Riordan Manufacturing. The recommendation recaps the results of the analysis phase activities, and together the team makes firm decisions about an alternative.

* Systems analysis would assist in understanding their existing system and identify problems which would help to improve the system.

Out of these factors, Supply Management, Project Tracking and Receiving are the core functionalities which are anyway required. Design and Foundation, Documentation and Request Definition are the supporting requirements which add value and enhance the quality of service or

After the proposed system is analyzed and designed, the actual implementation of the system occurs. After implementation, working system is available and it requires timely maintenance.