This question is of software architecture course

The section introduces the system requirements specification (SRS) for the <Sys Abbrev.> system to its readers.

This specification documents the system-level requirements for the <Sys Abbrev.> system.

The objectives of this specification of the <Sys Abbrev.> are to:

Provide a system overview of the <Sys Abbrev.> including definition, goals, objectives, context, and major capabilities.

To formally specify its associated:

Functional requirements.

Quality requirements.

Constraints.

The intended audiences of stakeholders for this specification of the <Sys Abbrev.> include:

…

This specification references or complies with the following documents:

…

This specification is organized into the following sections:

Introduction, which introduces the specification for the <Sys Abbrev.> to its readers.

System Overview, which provides a brief, high level description of the <Sys Abbrev.> including its definition, business goals, business objectives, context, and capabilities.

Functional Requirements, which specifies the functional system requirements in terms of a use case model consisting of each external’s use cases and use case paths.

Quality Requirements, which specifies the required system quality factors.

Constraints, which documents required architecture, design, and implementation constraints on the <Sys Abbrev.>.

This section provides a high level description of the <Sys Abbrev.> system including its definition, primary business goal, business objectives, context, and capabilities.

< The Global Personal Marketplace (GPM) system will be a global Web-based marketplace bringing together private individuals and small companies to buy and sell all manner of items. >

< The business goal of the Global Personal Marketplace (GPM) system is to take advantage of the Internet and World Wide Web to radically improve the way private individuals and small companies buy and sell items. >

<The business objectives of the GPM are to provide the following business benefits to its buyers, sellers, and owners. >

<The GPM will:

Provide its buyers with a huge selection of items (and sellers).

Enable its buyers to easily search for, find, and buy the items they want.

Enable buyers to buy items that they could not ordinarily find or afford.

Enable buyers to help set (and thereby minimize) the price of the items they wish to buy (e.g., via auctions and reverse auctions).

Make buying more convenient by allowing buyers to buy items:

Anytime (i.e., 24 hours a day and 7 days a week).

Anywhere the buyers have access to the Internet (e.g., at home, at work, and while traveling).

Minimize risks associated with buying over the Internet.

>

The section of the SRS specifies the functional requirements of the <Sys Abbrev.> in terms of use cases and their associated use case scenarios. The use case model is primarily organized in terms of the external actors that benefit from the use cases.

The following use case diagrams summarize the functional requirements for the <Sys Abbrev.>:

User Summary Use Case Diagram

Figure 1: User Summary Use Case Diagram

This subsection describes and specifies external roles, the associated responsibilities, and all use cases primarily driven by these external actors.

The subsection specifies the functional requirements primarily associated with players playing as a Native Tribe.

Definition

<An accountant is the role played by a GPM employee who performs accounting functions using the GPM. >

Responsibilities

< An accountant has the following responsibilities:

Set and maintain the billing cycle, fee schedule, and user restrictions.

Ensure that the GPM follows proper accounting procedures.

Report on the financial status of GPM.

>

Required Capabilities

<An accountant needs the following required technical expertise, experience, and training to effectively interact with the GPM:

Basic accounting skills

Use an accountant client computer to log onto and navigate the accountant user interface.

>

Use Case Diagram

Figure 2: Native Player Use Case Diagram

Use Cases

….

Use Case Requirement

< The GPM shall enable accountants to generate the following financial reports:

Feedback Summary Report

Fees Summary Report

Invoice Summary Report

Listings Summary Report

User Summary Report

>

Game Justification

…

…

Requirements Trace

< AVS OG-AC-1 Generate Financial Reports >

Use Case Paths

Normal:

…

Exceptional:

…

Path Requirement

…

Externals

Native Player

Preconditions

< The GPM has identified and authenticated the accountant. >

Interactions

…

…

Postconditions

< The accountant has the feedback summary report. >

< The feedback summary report shall contain the information specified in its associated data requirements. >

Categorization

Frequency: < Low (Monthly) >

Priority: < Medium >

This section specifies the required system quality factors that are not related to the specific functional requirements documented in the use case model.

<This subsection specifies the following requirements associated with the degree to which the system must be accessible to people with disabilities:

ACC-1) Any graphical user interfaces of the GPM shall be usable by persons with color blindness.

ACC-2) Any graphical user interfaces of the GPM shall use an adequate font size to be usable by persons with limited visual acuity.

>

< This subsection specifies the following requirements associated with the degree to which the system must support independent auditing of its transactions and finances:

AUD-1) The GPM shall maintain a record for 1 year of each invoice.

AUD-2) The GPM shall maintain a record for 1 year of each payment.

AUD-3) The GPM shall maintain a record for 1 year of each auction including:

Auction identifier

Item title and description

Auction type

Seller

Bid history

Auction results

Start and end dates and times

Winning buyers (if any)

Winning bid(s)

AUD-4) The GPM shall maintain a record for 1 year of each user inquiry and response.

>

This subsection specifies the following requirements associated with the degree to which the system must support the brand of GPMC.

The section documents the major architecture, design, and implementation constraints on the system.

< The subsection documents all required data design constraints. >

< The subsection documents all required constraints associated with minimum or actual hardware.

None

>

< The subsection documents all required software constraints. >

Private Ó 2019 by <Student Name> Page 12