THIS IS THE ASSIGNMENT THAT IS DUE. WE DID THE ASSIGNMENT #1 WITH STUDY DADDY AS WELL BUT UNFORTUNATELY, WE GOT VERY LOW GRADES. PLEASE CONSIDER THAT AND LOOKING FOR THE BEST GRADE NOW ON.
#INSTRUCTION ON HOW TO DO IT AND WHAT’S THE EXPECTATIONS OF PROFESSOR. JUST TO MAKE IT EASE I WILL POST THE ASSIGNMENT #1 INSTRUCTION AND ALSO HOW YOU”LL DID.
SYSTEMS ANALYSIS AND DESIGN [2242-INSY-3305]Fall 2024 | Instructor: Atieno A. AmadiAssignment-2 Process ModelInstructions:Draw a Level 0 Data Flow Diagram (DFD) for the Picnics R US case [See ‘Assignment#1’ onCanvas under ‘Assignments’]Guidelines:Data flow diagram (DFD) is a technique that captures the business processes of a firmand the data that pass among them. We use DFDs to describe the ‘to be’ system’sinteraction with its environment (i.e., external entities), processes, data flows, and datastores. The focus is on the processes and activities that are performed in the business.Hints:Use cases and DFDs are purposefully related – in that a well-constructed use casemakes developing a DFD straightforward. That is: The steps outlined in a use case canbe organized into logical processes on a DFD.Definitions:Use case: describes all the steps taken by a user to complete an activityEvery use case has three essential elements:the actor: the system userthe goal: the final successful outcomethe system: the process and steps taken to reach the end goalProcess: a series of steps taken to achieve a particular end goalModeling: making a representation of somethingProcess modeling: making representations of processesThe relationship between use case and process modeling:In process modeling, the steps/processes taken to reach the end goal in the usecase are represented using data flow diagrams (DFDs).
ASSIGNEMENT #1
SYSTEMS ANALYSIS AND DESIGN [2242-INSY-3305]Fall 2024 | Instructor: Atieno A. AmadiAssignment-1 Use CasesCase: Picnics R US [See ‘Assignment#1’ on Canvas under ‘Assignments’]A use case depicts a set of activities performed to produce some output result. Each use casehas a name, a number (ID), priority, actor, description, trigger (and trigger type), preconditions,normal course, postconditions, and possibly exceptions [See example in Figure 4-1 of the classtext]. The concept is useful in creating small, focused use cases, thereby breaking down theprocess into parts.For the Picnics R US case, show the essential use cases aimed at depicting user-systeminteractions in abstract, technology-independent steps. The objectives are to help everyonebetter understand the situation, and to help convey the required user-system interactions.Remember that use cases are helpful tools in understanding user requirements.Useful Guidelines Gather information for the use cases through the same requirements determination techniquesdiscussed in Chapter 3 of the class text [in this case – from the Picnics R US case]; Remember that use cases document one or more functional requirements outlined in therequirements definition; For process-oriented functional requirements (i.e., things the system must do), suggest a directaction resulting from an external (time-driven) event; For information-oriented functional requirements (i.e., content the system must have), suggestthings that happen involving information (or time trigger) to collect or produce information.Steps for Writing Use Cases:1. Identify the use cases2. Identify the major steps within each use case3. Identify elements within steps4. Confirm the use case
AND THE CASE YOU DID IT WAS. I ATTACH THAT FILE.
