Using Microsoft Visio, develop a Use Case Diagram for the business scenario involving the following, homework help

User Generated

TKVNBLHNA

Computer Science

Description

about the Mid-Century Modern Décor Unlimited (MCMDU) move forward into the Requirements Structuring Phase (see textbook Chapter 7) of the SDLC.

Task

- Using Microsoft Visio, develop a Use Case Diagram for the business scenario involving the following actors: Inventory shipping/receiving clerk, inventory information systems manager, inventory information systems analyst, operations manager, sales manager, and warehouse manager. Note: you may add any other "actor" roles that you believe are relevant. Provide your use case diagram on a separate page in the same Visio file containing your DFD diagrams. See the discussion and examples of Use Cases In Appendix 7A of Chapter 7 (pages 217-231).Note: you make make reasonable assumptions regarding any information that you believe may be missing or incomplete in the above specifications as long as you clearly state all assumptions in a text box on the DFD and/or Use Case diagram documents.

Unformatted Attachment Preview

Case – Mid-Century Modern Design Unlimited Business Case on Mid-Century Modern Décor Unlimited Background Information Mid-Century Modern Décor Unlimited (MCMDU) is a manufacturing business specializing in manufacturing and selling décor items targeted at the global mid-century modern décor market (see this Wikipedia entry for information on this décor style). Currently in its tenth year of operations, MCMDU has grown from a small manufacturing operation with a catalog of ten interior décor items to one that now manufactures in excess of 60 décor items, imports approximately 200 décor items from manufacturing business partners in Asia, and operates two outlet stores within a 250 mile radius of its U.S. manufacturing plant location. The owner of MCMDU, Alexis Harrison, has indicated that the company now has over 80 full-time employees in purchasing, manufacturing, logistics, marketing/sales (wholesale and retail), customer service, inventory management, information technology, human resources, and accounting job roles. In addition to Ms. Harrison, company management includes two vice presidents, one for operations and one for sales, supported by an administrative office staff of five. Ms. Harrison has contracted with your consulting team to manage the design, development, and implementation of a state-of-the-art business system to manage and improve the overall efficiency of the inventory management (which is impacted by manufacturing, marketing/sales, customer service, and logistics processes) in this business environment. Ms. Harrison has specifically identified the need for information systems support to enable more efficient inventory management in dealing with overall inventory maintenance and information access for support of both ongoing company operations and decision making. Ms. Harrison has specified that this system must be complete and operational by March 1, 2018 (it is now June 2017). In addition to the summary above, she has provided you with the following background information about the business: MCMDU has undergone a radical change in its sales channels from one primarily based on salespeople selling to bricks-and-mortar retailers and wholesalers to one in which over 80% of its sales volume is now generated by sales to e-commerce retailers in the global e-commerce arena. Because of this substantial change in sales channels, the existing company processes of inventory management and sales fulfillment are under severe stress in trying to keep up with the demand for product line inventory item information by customers, particularly the e-commerce retailers who are now accounting for the bulk of the company’s sales volume. It is typical that each e-commerce retailer will require a template specific to their own product detailing methodology, so the new system must support multiple potential templates. Currently, the two company employees supporting the inventory management function are maintaining nine Microsoft Excel 2010 workbooks that provide, collectively, comprehensive information on the company’s inventory, which includes both self-manufactured items and items manufactured by the Asian manufacturing business partner companies. Ms. Harrison has told you that the inventory management employees have made her aware of several inefficiencies in their current inventory management system and the associated resources. These employees have reported that different ecommerce retail customers have different inventory information requirements for doing business with MCMDU and that several of those e-commerce retailers require the use of their own proprietary templates to support the provision of information on MCMDU’s items purchased for resale by those companies. At least one of the e-commerce retailers has told Ms. Harrison that the more information that they are able to display on the physical specifications of décor items, the better they tend to sell on their e-commerce website. The differential requirements from multiple e-commerce retailer customers have resulted in processes requiring six to eight hours to retrieve and format the inventory information required on ordered items by just one of those e-commerce retailing customers. This excessive effort is currently necessitated by manually extracting the requested inventory information from the nine Excel workbooks and then placing it in a template containing the required format for that customer. Obviously, MCMDU has a critical need for substantial improvement in processes related to the provision of inventory information for e-commerce customers. Ms. Harrison has told you that your budget for the analysis, design, and implementation involved in this project is $150,000. She has identified the following major requirements for the completed and implemented inventory management system: 1. All inventory information maintained in a single information system 2. Replication of all inventory information in an off-site location to support disaster recovery 3. Easy-to-use, highly secured access for company employees 4. Full query and reporting functionality to support decision making for manufacturing and sales 5. Cost-effective information extraction processes to support e-commerce retailers’ demands 6. Complete end-user and technical documentation to support ongoing use of the system At this point, she has provided you with only the above-described information about the current inventory information provision processes used by the company . She has summarized the current situation as "slow, tedious, and unworkable for supporting both current information demands and anticipated future increases in both an expanded inventory line and in demand based on increasing sales volume to e-commerce retailers." Chapter 7 Notes Requirements Structuring Process modeling – graphically represents functions or processes that capture, manipulate, store, and distribute data between system and environment Data Flow Diagrams (DFD) – picture of the movement of data between external entities and processes and data stores within a system Start with Context data flow diagram – shows scope, birds eye view DFDs physical system – adequate detail only DFDs logical system DFDs new logical system – DFD Mechanics – used for both physical and logical information systems. Only four symbols are used – very simple system Useful for depicting logical information flows start with logical, move into physical Tool sets for DFDs, figure 7-2, two different types of tool sets, same purpose Process – work or actions performed on data (inside the system) Data store – data at rest (inside system) Source/sink – external entity that is origin or destination of data (outside system) Data flow – arrows depicting movement of data Context diagram – overview of organizational systems – shows system boundaries, external entities, major information flows (birds eye view), shows only one process symbol, no data stores Level 0 – diagram – more detail, process decomposition, represents systems major processes, data flows, and data stores at a high level of detail: processes are labeled 1.0, 2.0, etc, this indicates predecessor for decomposition Two DFD guidelines that apply: 1) the inputs to a process are different from the outputs of that process – the process transforms inputs into outputs 2) Objects must have unique names (see table 7-2 for other rules) Functional decomposition – iterative process of breaking a system description down into finer and finer detail, continues until no sub process can logically be broken down any further Primitive DFD – lowest level of DFD (can’t be broken down anymore) Level-1 diagram results from decomposition of Level-0 diagram Level-n diagram is a DFD diagram that is the result of n nested decompositions from a process on a level 0 diagram Level -1 DFD Level-n DFD Balancing DFDs Conservation Principle – conserve inputs and outputs to a process at the next level of decomposition Balancing – conservation of inputs and outputs to a data flow diagram process when that process is decomposed to a lower level Balanced means: number of inputs to lower level DFD equals number of inputs to associated process of higher level DFD Number of outputs to lower level DFD equals number of outputs associated process of higher level DFD Data flow splitting – when a composite flow at a higher level is split and different parts go to different processes in the lower level DFD, remains balanced, just split into two lower level parts Current Physical – process labels identify technology used to process the data Current Logical – physical aspects of system are removed as much as possible New Logical – includes additional functions, obsolete functions removed New Physical – represents the physical implementation of new system Guidelines for drawing DFDs Completeness – the extent to which all necessary components of a DFD have been included and fully described Consistency – the extent to which information contained on one level of a set of nested DFDs is also included on other levels Timing – time is not depicted well, draw DFDs as if system has never started and will never stop Iterative Development – expect to draw diagram several times before reaching closest approximation Primitive DFDs – lowest level of decomposition for a DFD Rules for stopping decomposition 1) when each process has been reduced to a single decision 2) when each data store represents data about a single entity 3) when the system user doesn’t care to see any more detail 4) when every data flow does not need to be split further 5) When you believe you have shown each business form or transaction 6) when you believe that there is a separate process for each choice Gap analysis – process of discovering discrepancies between two or more sets of data flow diagrams Decision tables – matrix representation of the logic of a decision which specifies the possible conditions for the decision and the resulting actions. Best used for complicated decision logic Rows are Conditions/Courses of action, Columns are rules Condition Stubs – part of a decision table that lists the conditions relevant to the decision Actions Stubs – part of a decision table that lists the actions that result for a given set of conditions Rules – part of a decision table that specifies which actions are to be followed for a given set of conditions Indifferent condition – in a decision table, condition whose value does not affect which actions are taken for two or more rules Procedure for creating decision tables 1) name the conditions and the value that each condition can assume 2) name all possible actions that can occur 3)list all possible rules 4)define the actions for each rule 5)simplify the decision table Questions 1) Describe dimension of system processes illustrated with data flow diagramming, why do we do data flow diagramming? 2) Explain why that are multiple levels of DFD diagrams when they are used to depict system processes 3) Explain in simple terms what is meant when it is said that data flow diagramming is a process of functional decomposition 4) How can you determine when a data flow diagramming effort is complete? 5) Identify and explain the major components used in a decision table 6) How does the construction of a decision table help in structuring system process requirements? Chapter 7 Appendix A Use Cases Use case is a depiction of a systems behavior or functionality under various conditions as the system respond to request from users Actor is an external entity that interacts with the system – stick figure is a role Most actors represent user roles, actor is a role, not a specific user Abstract use case – when a use case is initiated by another use case, use case represents complete functionality of the system Use case diagram – picture showing system behavior, along with the key actors that interact with the system Symbol set: use case, actor, boundary, connection System boundary is the dividing line between user, represents all of the relevant use cases Connection – association between actor and a use case. Solid line shows that actor is involved in particular system function. Extend relationship – association between two use cases where one adds new behaviors (dotted line) Include relationship – one use case uses functionality contained in another Written use cases – template that shows title, actor, level, stakeholders in a use case Level – perspective from which a use case description is written, ranging from high level to extremely detailed Chapter 7 Appendix B Activity Diagrams Activity diagrams – show the conditional logic for the sequence of system activities needed to accomplish a business process. Clearly, shows parallel and alternative behaviors. Can be used to show logic of use case Use Activity Diagrams to: Depicts flow of control from activity to activity Help in use case analysis to understand what actions need to take place Help in identifying extensions in a use case model work flow and business processes Model sequential and concurrent steps in a computation process Activity-behavior that an object carries out while in a particular state (rectangles) Transition – movement of activity from one activity or state to another Branch – diamond symbol containing a condition whose results provide transitions to different paths of activities Synchronization bar – horizontal or vertical bars denoting parallel or concurrent paths of activities Fork – beginning of parallel activities Join – the end of parallel activities Swim Lanes – columns representing different activity units of the system Chapter 7 Appendix C Sequence Diagrams Sequence diagrams – depicts the interactions among objects during a certain period of time Generic form – shows all possible sequences of interactions Instance form – shows sequence for only one scenario Objects- boxes at top of diagram Lifeline – time during which an object exists Message – means by which objects communicate with each other Activation – time period during which an object performs an operation Synchronous message – type of message in which the caller has to wait for receiving object to finish executing the called operation before it can resume execution itself Simple message – message that transfers control from the sender to the recipient without describing the details of the communication Asynchronous message – message in which the sender does not have to wait for the recipient to handle the message Differentiate the purposes of building use case diagrams, activity diagrams, and sequence diagrams (it would be helpful to identify the dimensions of system logical structure that each of these methods depict)
Purchase answer to see full attachment
User generated content is uploaded by users for the purposes of learning and should be used following Studypool's honor code & terms of service.

Explanation & Answer

Please let me know if there is anything needs to be changed or added. I will be also a...


Anonymous
Really helped me to better understand my coursework. Super recommended.

Studypool
4.7
Trustpilot
4.5
Sitejabber
4.4

Related Tags