How Important Are System Analysis and Especially Requirement Analysis to the Success of Software Development

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.

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.

In this class, we’ve stressed the importance of various system analysis and design tools and techniques. By now you should have a “toolbox” full of useful design and analysis tools. List the tools in your toolbox and then write one short paragraph on how you can/will apply them in your careers, lives,

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 next step in the process is system analysis. This second stage involves gathering requirements, such as documenting the strengths and weaknesses of the current system, having discussions with the users to understand their roles and needs. This is an integral part of the life cycle as employees are the most important asset a company has. Baya, Gruman, & Mathaisel state, “information technology

They may also devise ways to apply existing systems’ resources to additional tasks. Most systems analysts work with specific types of computer systems- for example, business, accounting or financial systems or scientific and engineering systems –that vary with the kind of organization.” (Computer Systems Analysts, 1)

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

System Analysis is the study where detailed information about the components and requirements of a system, the information needs of an organisation, the characteristics and current components of the systems and the user functional requirements of the systems that is proposed system.

This is my reflective consolidation paper which is an end of course assignment and writing this essay about the experience I had while studying the course System analysis and design. When I went to my advisor for advising courses then she told me about System analysis and design and explained me clearly about this course then this course made me realise that I have a lot to learn and found it as very interesting and challenging.

System development can generally be thought of having two major components: systems analysis and systems design. In System Analysis more emphasis is given to understanding the details of an existing system or a proposed one and then deciding whether the proposed system is desirable or not and whether the existing system needs improvements. Thus, system analysis is the process of investigating a system, identifying problems, and using the information to recommend improvements to the system. System design is the process of planning a new business system or one to replace or complement an existing system.

Systems analysis refers to a problem solving technique where a business or procedure is studied and the goals are identified in order to create information systems to help the business achieve their goal more efficiently and easier. Systems analysts obtain feedback from the system users in various ways e.g. interviews, questionnaires etc. More importantly they find out from the users what their specific requirements are regarding the proposed system and then use the information obtained to formulate requirements for the system, the system is then written ensuring that all the requirements and expectations are met.

Though many people interchange system engineering models and software engineering life cycle models, they are defined as two different approaches to software development. System engineering is the technical and technical management process that results in delivered products and systems that exhibit the best balance of cost and performance. As the program progresses from one phase to the next one, so does the system engineering process. It deals with the overall management of engineering project during their life cycle. Its main focus is knowing what the clients and end users wants and needs are satisfied and developing just that all the way through the system’s entire life cycle. Whereas, on the other hand, software engineering focuses on the quality of the product or system, how cost effective it is, is it done within the time-constraints given, whether it is easy to maintain and enhance, and does it work as the requirements defined. Its main focus is on delivering a product that meets the requirement specifications. There are so many models to choose from, as it all depends on what the project needs and entails. Depending on the requirements, allows for the choice of what mode to use.

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