IFN552 System Analysis and Design Assignment 1 Sample

Sample IFN552 System Analysis and Design Assignment 1

In this Assignment, you will take what you have learnt in weeks 1, 2 and 3 and apply this to a case. You will develop a list of questions that you would ask key stakeholders to elicit requirements, distil stakeholder needs into functional requirements in a Requirements Matrix, draw a Use Case Diagram and Activity Diagram. You will also justify your designs in short descriptions accompanying each of these outputs.

1. Read the Criterion-Referenced Assessment Rubric at the end of this document.

2. Read Case 1 (below) which pertains to all elements of this assignment.

3. Develop and document a list of questions for two of the key stakeholders to specifically gather functional requirements. Aim for approximately 10 key questions for each stakeholder type (you can also choose to add follow-up sub-questions if necessary).

4. Try out your questions on the Grower, Customer and Business chatbots (available by the end of Week 1) on Slack by entering a conversation with each under the “Apps” dropdown in the IFN552 Slack channel. Note the chatbots are there to provide you with an opportunity to practice asking stakeholder questions and to provide additional ‘bonus’ information about the case; they will not be able to answer all of your questions, but can help you explore and brainstorm some of the needs for the stakeholders. Please do not rely solely on these to develop your list of requirements.

5. Develop a Requirements Matrix to show the functional requirements of the new system. Aim for:

a) 15 Essential Functional Requirements

b) 5 Desirable Functional Requirements

c) 1 Optional Functional Requirement

You should include the suggested number for each priority of requirements, totalling around 21 Functional Requirements in your matrix. A small amount less or more may be ok depending on the quality of the ones you include, but you will need to stay around the number stated above. Whilst each will have certain priority, and the list may not be comprehensive, you need to ensure that all are relevant to the case and are concise, specific, measurable and actionable.

6. In 250 words or less, justify your choices (i.e. How/why did you decide to split the system into the modules you chose? How did you decide on priorities? Is there a particularly novel or unusual requirement that you have identified – if so, how does it meet the needs of your stakeholders? etc.).

7. Draw 1 (one) Use Case Diagram representing the new integrated system described in the case.

a) Aim to include around 15-20 Use Cases in your diagram (no more than 23). Ensure that the use cases you do include are important and relevant to the process being represented.

8. In 250 words or less also introduce your use case diagram (i.e. what is it describing? At which points do users interface with the system? What is outside the scope of your diagram? Etc.).

9. Draw an Activity Diagram, representing how a grower would order a kit on the website, monitor the growth of their produce, organize a swap for their grown produce with replenishment seeds/cuttings and

a customer eventually ordering some of that produce via the website.

You can start with the following assumptions:

a) Assume that the grower and customer are already in logged in states at the beginning of their processes (i.e., no need to include activities involved in login/register)

b) The delivery process is handled by an external company. There is therefore no need to include any activities associated with the delivery process other than those that involve the system being designed and/or other actors in the process

Remember to balance detail with clarity in your diagram. Take note of the following guidelines regarding scope:

a) Use around 2-3 swimlanes to differentiate system activities initiated by different actors. For activities performed by a subsystem with no interaction with an actor, you may use a separate “system” swimlane, however, ensure all other activities performed in actor swimlanes describe system interactions.

b) Use up to 60 shapes – ideally around 50 shapes – (shapes include boxes, decision nodes, fork and join, arrows, etc.) to show the process of user activities.

c) Use decision nodes two or three times and fork and join two or three times in your model.

d) Preferably, your activity diagram will be vertical, rather than horizontal (this will make it easier when merging it into the submission PDF).

10. Write a short description of your Activity Diagram in 250 words or less. Imagine you are presenting it to a set of stakeholders and you need to introduce concisely what it is showing (~1-2 sentences) and mention a few interesting/important activities or flows, as well as parts where you have made assumptions (~3-4 sentences).
Note that it’s important to practice this skill, as you will need to contextualise designs/diagrams when you create reports/presentations.

Solution

List of questions

Stakeholder #1: Growers

1. How frequently would you like to receive updates on the growth of your plants?

2. What kind of data would you like to see about the plants' growth? (e.g. temperature, humidity, light levels)

3. How would you prefer to receive updates on the growth of your plants? (e.g. email, SMS, app notifications)

4. What information would be helpful for you to know about the exchange process with delivery personnel?

5. Would you prefer to have the option to customize the seeds/cuttings you receive in your kit?

6. What would be your preferred method for providing feedback on the Grow Kit and the plants' growth?

7. How would you like to be paid for the produce you grow? (e.g. bank transfer, PayPal)

8. What kind of support would be helpful for you during the growing process? (e.g. online tutorials, live chat support)

9. How frequently would you like to receive new seeds/cuttings?

10. Would you be willing to provide additional information about your location and growing conditions to help improve the Grow Kit and plant growth?

Stakeholder #2: Website Users

1. What kind of user account management features would you like to see on the website?

2. How would you like to receive notifications about inventory levels and forecasts?

3. What kind of analytics would be helpful for you to have access to about plant growth and inventory management?

4. What kind of user data would be helpful for the website to collect to improve the user experience?

5. How would you like to be able to communicate with growers through the website? (e.g. messaging, chat)

6. What kind of security measures would you like to see implemented on the website?

7. What kind of payment processing system would be most convenient for you to use?

8. What kind of customer service features would be helpful for you to have access to on the website?

9. What kind of reporting features would be helpful for you to have access to on the website?

10. How frequently would you like to receive updates about the website's functionality and new features?

Requirement matrix

Requirements Matrix for Micro-Farming Start-Up

(Rodriguez et al., 2022)

The essential functional requirements are necessary for the system to function as intended. Without the sensor data collection, display, and algorithm integration, the business cannot accurately forecast produce availability and manage inventory levels. Produce collection and replenishment, along with the delivery driver booking system, are required to manage the exchange of produce and replenishment kits between the business and Growers. The integration of Grow Predict with the online store inventory management is essential to ensure accurate stock levels and provide customers with available produce. Lastly, Growers require the ability to select grow kit size and type of produce to grow, and to receive starter kits with all necessary components (Wang et al., 2020).

The desirable functional requirements, while not critical to the system, provide additional benefits to the stakeholders. Allowing customers to customize produce boxes and providing subscription-based discounts can increase sales and customer loyalty. Nutritional information can appeal to health-conscious customers, and feedback from Growers can improve the quality of the products. Alerts to Growers can help ensure healthy plant growth. The optional functional requirement enables Growers to sell excess produce to the online store, providing an additional revenue stream for Growers and increasing the variety of available produce for customers. However, this functionality is not essential to the system and may require additional resources to implement (Rodriguez et al., 2022).

The functional requirements for the assignment help have been prioritized based on the impact on the business and the needs of the stakeholders. The system has been divided into modules to ensure efficient development and management of each aspect.
Use case diagram

Figure 1 Use case Diagram.

The use case diagram describes the interactions between the actors and the system at the various touchpoints. Growers interact with the system through the Grower Portal, where they manage their Grow Kits and sell their produce. Customers interact with the system through the Online Store, where they browse and purchase produce boxes. The GrowPredict Algorithm interacts with the system to provide inventory forecasting based on the sensor data from the Grow Kits (AL-Msie'deen et al., 2022). Outside the scope of this diagram are the technical details of the system, such as the database and server infrastructure, and the specifics of the sensor data collection and analysis. The diagram shows the relationships between the actors and the system components and illustrates the flow of data and actions between them. It is important to note that the scope of the diagram does not include specific details about the sensors or the algorithm, but rather focuses on the high-level interactions between the actors and the system components (Arifin & Siahaan, 2020).
Activity diagram

Figure 2 Activity diagram.

The Activity Diagram is a visual representation of the steps involved in the Grower portal, from purchasing a kit to harvesting produce and replenishing it with new seeds/cuttings. The diagram shows the flow of activities, including the monitoring of plant growth, the notification system for harvest, and the scheduling of pickup/delivery times. It also includes assumptions, such as the delivery driver being booked automatically and the company paying for the products based on the weight of usable produce. An interesting flow is the integration of GrowPredict, which forecasts when certain products will be available and in what numbers, and how it helps connect the online store and the Grower portal (Bakar et al., 2020).

References

Fill the form to continue reading

Sample IFN552 System Analysis and Design Assignment 1

GRAB IT ASSIGNMENT HELP: A+ GRADE ASSURED Place Your Order Now and Get Up To 20% Discount!