Press "Enter" to skip to content

Unit 2 -Group Discussion: Functional and Non-Functional System Requirements

0
(0)

Group Discussion: Functional and Non-Functional System Requirements

The success of any IT project depends on clearly understanding what will satisfy stakeholder expectations. These expectations can be expressed as a collection of functional and non-functional system requirements.

To prepare for this Discussion, review the Case Study and identify at least two functional and at least two non-functional requirement for the system. Consider ways to divide the effort of creating system requirements and a tool for drawing use case diagrams.

By Day 2

Post a short description of the requirements you identified. Explain how you derived them from the case study. Also explain how you might use a tool to illustrate the functional system requirement in a use case diagram.

Then, propose how your group might divide the effort to create the list of system requirements and the use case diagram. Suggest an editing tool to be used by the group to complete the use case diagram.

Read all of your group members’ postings.

By Day 4

Respond to all of your group members’ postings. Ensure that everyone agrees on a drawing tool and the division of labor, including who is responsible for compiling and submitting the final documents.

Important Note: In this Discussion, you read and respond only to members of your own Project Group. Therefore, after clicking on the Post to Discussion link, you will need to click on the Group Discussion Board link and then enter the Discussion Forum.

Submission and Grading Information

Grading Criteria

To access your rubric:Unit 2 Discussion Rubric

Post by Day 2 and Respond by Day 4

To participate in this Discussion:Teams


Group Project: Functional and Non-Functional System Requirements

Analysts must do a great deal of translation between the user’s description of new or updated application software and the detailed specifications for building that software. The Case Study provides descriptions from which your group may develop appropriate functional system requirements. You will not find explicit statements about non-functional requirements. Instead, your group must infer what the system should include. Focus on items related to hardware, software, security, and cost. You may leave some of these non-functional requirements somewhat open-ended and refine them later in the project as you gain a more complete understanding of the system.

To prepare for this assignment, meet and brainstorm ideas with your group members using your knowledge from previous courses. Decide whether to divide functional requirements among group members by subsystem, or to share equally across the system. Consider how group members will review the functional requirements and ensure that they are complete and consistent. Consider when and how the group will determine non-functional requirements.

As a group, compile and agree on the complete list of functional requirements. Define at least four modules (sub-systems) to organize the main functions of the system. Common modules include Financial (General Ledger, Accounts Payable, Accounts Receivable) Human Resources (Time Entry, Payroll, Benefits Administration, Position Management), and Manufacturing (Shop Floor Control, Quality Control, Bill of Materials, Inventory).

Define non-functional requirements for the technology. These requirements might include: cloud vs. on-premises, database, operating system, programming languages, computing hardware, network components, interface or integration requirements to other applications, and IT support staff estimates. Project the cost of building, implementing, and maintaining the system for the next 5–7 years.

Perform the following tasks:

By Day 4

Individually post to the group discussion board the following items:

  • A suggested list of functional system requirements divided into at least four modules (sub-systems) that represent the entire system as described in the case study.
  • A suggested list of non-functional requirements for the system.
  • Justify your suggestions.

By Day 6

As a group

  • Develop a group list of functional requirements divided into at least four subsystems.
  • Develop a group list of non-functional requirements.
  • Confirm the name of the member of the group responsible for compiling and submitting the group document for week 2.

By Day 7

Submit the following in a single group document:

  • A list of all functional requirements of the system divided into at least four sub-system.
  • A list of all non-functional requirements of the system.
  • A summary of the contributions made by each member of the group. (Do not copy and paste from the discussion board). Include the self-reported number of hours each group member contributed to the project.
  • A brief analysis of the group process, group strengths, and group concerns for the week.
  • The name of the group member responsible for compiling and submitting the group results for this week.
  • The names of the group members responsible for compiling and submitting the group results for weeks 3 and 4 of the project.

Important Note: A Discussion thread has been made available for the Group Project(s) in each Unit for collaboration with your group members. You can access these Discussion threads by clicking on Groups on the left navigation bar, entering your assigned group, clicking on the Group Discussion Board, and then entering the Project Forum. To collaborate on this Assignment:Teams

Submission and Grading Information

To submit your completed Assignment for review and grading, do the following:

  • Please save your Assignment using the naming convention “UN2Proj1+last name+first initial.(extension)” as the name.
  • Click the Unit 2 Project 1 Rubric to review the Grading Criteria for the Assignment.
  • Click the Unit 2 Project 1 link. You will also be able to “View Rubric” for grading criteria from this area.
  • Next, from the Attach File area, click on the Browse My Computer button. Find the document you saved as “UN2Proj1+last name+first initial.(extension)” and click Open.
  • If applicable: From the Plagiarism Tools area, click the checkbox for I agree to submit my paper(s) to the Global Reference Database.
  • Click on the Submit button to complete your submission.
Grading Criteria

To access your rubric:Unit 2 Project 1 Rubric

Check Your Assignment Draft for Authenticity

To check your Assignment draft for authenticity:Submit your Unit 2 Project 1 draft and review the originality report.

Submit Your Assignment by Day 7

To submit your Assignment:Unit 2 Project 1


Group Project: Use Case Diagram

A use case diagram helps both technical and non-technical users understand the functional requirements for a system. Review your previous work with use cases or search the Internet, if necessary.

Meet with your group members and develop a high-level use case diagram based on the functional requirements for the case study. Divide the diagram by the sub-systems specified in the functional requirements. Capture all of the functional requirements, but it is not necessary to develop detailed use cases for each sub-system and function.

Perform the following tasks:

By Day 6

Individually post to the group discussion board the following items:

  • A suggested high-level use case diagram that captures all functional requirements divided into sub-systems.

By Day 7

As a group

  • Develop a group high-level use case diagram that captures all functional requirements divided into sub-systems.

By Day 7

Submit the following in a single group document:

  • A group high-level use case diagram that captures all functional requirements divided into sub-systems.
  • A summary of the contributions made by each member of the group. (Do not copy and paste from the discussion board). Include the self-reported number of hours each group member contributed to the project.
  • The name of the group member responsible for compiling and submitting the group results for this week.

Important Note: A Discussion thread has been made available for the Group Project(s) in each Unit for collaboration with your group members. You can access these Discussion threads by clicking on Groups on the left navigation bar, entering your assigned group, clicking on the Group Discussion Board, and then entering the Project Forum. To collaborate on this Assignment:Teams

Submission and Grading Information

To submit your completed Assignment for review and grading, do the following:

  • Please save your Assignment using the naming convention “UN2Proj2+last name+first initial.(extension)” as the name.
  • Click the Unit 2 Project 2 Rubric to review the Grading Criteria for the Assignment.
  • Click the Unit 2 Project 2 link. You will also be able to “View Rubric” for grading criteria from this area.
  • Next, from the Attach File area, click on the Browse My Computer button. Find the document you saved as “UN2Proj2+last name+first initial.(extension)” and click Open.
  • If applicable: From the Plagiarism Tools area, click the checkbox for I agree to submit my paper(s) to the Global Reference Database.
  • Click on the Submit button to complete your submission.
Grading Criteria

To access your rubric:Unit 2 Project 2 Rubric

Check Your Assignment Draft for Authenticity

To check your Assignment draft for authenticity:Submit your Unit 2 Project 2 draft and review the originality report.

Submit Your Assignment by Day 7

To submit your Assignment:Unit 2 Project 2

How useful was this post?

Click on a star to rate it!

Average rating 0 / 5. Vote count: 0

No votes so far! Be the first to rate this post.

inciteprofessor
inciteprofessor

Inciteprofessor is a Master Holder in Actuarial Science from the World's Best Universities. He also possesses a Bachelor degree in Computer Science and Cyber Security. He has worked with many freelance companies including Freelancers, Fiverr , Studybay, Essayshark, Essaywriters, Writerbay, Edusson, and Chegg Tutor. He offers help in research paper writing & tutoring in Mathematics, Finance, and Computer Science field.

View all posts

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.