Software Requirements Analysis Chapter 2

The arrangement of the organization's computing hardware, network infrastructure, and system software. Basically, it describes the physical structure of their IT setup.

This includes the information systems, subsystems, and supporting technology that the organization relies on to function. It's essentially the software side of the IT picture.

This system handles the entire process of buying and selling goods, from receiving orders to shipping products. This is a core function for a company like RMO.

This system deals with customer interactions, helping them with orders, questions, and any issues they might have.

This system manages orders placed through phone or mail. It's important for businesses that rely on traditional order channels.

This system handles orders and transactions carried out at physical RMO stores.

This system is specifically designed for managing trade shows, which are important for RMO to showcase their products.

This is the proposed new system for RMO. It aims to consolidate sales and marketing operations by integrating various existing systems.

A subsystem within CSMS responsible for receiving orders and ensuring their timely delivery, including tracking shipments and customer feedback.

A subsystem within CSMS that manages customer information, including purchase history, rewards, and loyalty programs.

A subsystem within CSMS that focuses on marketing strategies, promotions, and building partnerships.

The process of understanding and discovering the complex business rules and processes that are involved in a system.

A well-defined, structured approach for developing and implementing information systems that includes planning, analysis, design, implementation, testing, and maintenance phases.

The initial phase of SDLC where the problem or opportunity is identified, an approval is obtained, and a project plan is developed.

The core of systems analysis where the focus is on understanding and documenting the existing system.

The process of collecting information about a system's needs and goals.

Describing what a system should do, and how it should behave.

Listing the various features, qualities, and attributes that a system must have.

Prioritizing requirements based on their importance and value.

Creating the way users will interact with the system.

Getting feedback from users to ensure the system meets their needs.

A detailed description of the functions, behaviors, and qualities of a software system.

A list of things that the software needs to be able to do.

They focus on how easy and enjoyable the system is to use. They address user experience, design, and accessibility of the system.

They specify how well the system performs under various scenarios. They address factors like speed, response time, and resource usage.

These requirements outline security measures to protect the system and its data from unauthorized access, modification, or disclosure.

Individuals or groups with a vested interest in the success of a system.

Individuals within the organization who have a stake in the system's success (e.g. employees, managers).

Individuals or groups outside the organization who have a stake in the system's success (e.g. customers, suppliers).

These requirements define constraints on the system's design, implementation, and development. Examples include specific programming languages or hardware limitations.

Requirements serve as a common understanding between developers, clients, and users. They clarify what the software should achieve.

Requirements help define the project's boundaries. They ensure everyone knows what's included and excluded from the software.

Requirements are the foundation for the software design. They guide developers in creating a solution that meets the specified needs.

Requirements provide checkpoints for verifying that the software meets the intended goals. They serve as criteria for testing and validation.

Requirements can change over time. Effective management of change is crucial, involving version control and change requests.

Ambiguous or incomplete requirements can lead to confusion during development. Clear and precise requirements are vital.

Balancing the needs and expectations of various stakeholders can be challenging. Effective communication is essential.

Functional requirements describe the core functions of the system. They specify how the system should behave and what users can do with it.

The process of defining the specific functionalities and features of a system, alongside its non-functional attributes like usability, reliability, and security.

A detailed plan that outlines the organization's technology infrastructure, including hardware, network, and system software.

A plan that outlines the specific information systems, subsystems, and supporting technologies that the organization uses to function.

A set of requirements for a system, organized by functional, usability, reliability, performance, and security.