Management

Expectations for Group Project (MIS 300 / MIS 301, Fall 2015) Scope and Deliverable: The project is to describe the information flow within a small organization or a department or business function within a larger organization. It could be a university department or a private business where one of the group members works. It might also be a store or business that you simply ask for some time to investigate. What each group will deliver is the analysis segment of the SDLC. This will include: • A hypothetical requirements document for an information system that will serve that business or department (Inputs, outputs, processes, performance requirements, control requirements) • A functional decomposition diagram, showing the functions you wish to model. If you are doing a department or business function, the FDD should show that function in the larger context of the organization (refer to the ‘library’ example on page 140 (VISIO, Word, or Power Point) • A context diagram for the organization or function you will investigate. (Visio, Word, or Power Point) • At least three use cases describing processes in the organization or department and how users interact with it. (VISIO) • A top-level diagram (diagram 0) showing at least three processes, one data store, two external entities, and data flows properly depicting how data flows among the objects (processes, data stores, and external entities. All data flows, processes, and external entities must be properly named. The diagram must agree with the context diagram from above. (VISIO) • An ‘Explosion’ of each of the three (or more) processes, each of which will show at least two sub-processes. Each explosion must properly number the sub-processes, and the data flows shown must be in agreement with the ‘parent’ process. • A data dictionary, showing for each data flow or data store, the complete list of data elements involved with appropriate metadata (see page 199). • A process description for each bottom level (primitive) process. There are multiple approaches to creating process descriptions (pseudocode, decision tables, decision trees….). Any of them is OK, and you don’t have to use the same one for every process. You will use the file exchange area to submit and share the various VISIO, Word, Power Point, and other files that are generated. In addition, two copies of a printed final report must be submitted (one for me, one for the client). The final report will consist of all the items listed above, printed and logically organized. Chapter 4 Requirements Modeling I 0 analysts use functional decomposition diagrams, business process models diagrams, and Unified Modeling Language diagrams. Any of these cated with CASE tools or stand-alone drawing tools if desired 'L.."' Video Learning Session Functional Decomposition Diagrams Video Learning You have an MIS CourseM ate access code., can launch Inter... Sessions tobelP You understands ystems development concepts and practice your skills. You can watch the video on your computer or mobile device. and pause. rewin. or replay the session at any time.To log on to the MIS CourseMate site at www.cengagbain.com, Y°u;iiii:jsstsecsrs7inei::buoduetTu=teiCedo:poensal'agr trahMc'Dki)s).Y0,11 about and rad aC I'rudr,e; rustotnc lntcgrac an ,r;,"03;r, why they are important, how to use FDDs to model business function and processes, and how to use CASE tools to create FDDs. Workis diagr31 grams prOcreS Figure which \ functionald decomposition diagram 11 I the D (FDD) is a top•down and o arc do representation of a funs• — mode tion or process. Using an FDD, an analyst can j 1= eT:r.,,„.' show business functions ' and break them down Functional Decomposition Diagrams into lower-level functions and processes. Creating an FDD is similar to drawing an organization chart — you start at the top and work your way cair;Vrlitr"hr„! st"".":"'.“:"AL.1 3, rem drawn with the FIGURE 4 Analyst (2. Thls FDD shows a library mum,- rep The CASE toots too,..D, can be used at „O.., subprocesses. .0arations function includes twe Use Part 8 of the si-veral stages of systems system, development. During r uirements modeling, analysts use FDDs to model business functions and sh; how they are organized into lower•level processes. Those processes translate program modules during application development. ate provide an over Business Process Modeling obese coot,. cum ro A, you learned in Chapter I, a business process model (BPM) describes 011,:.?r! ea n raw a about business process, such handling an airline reservation, filling a product updating customer account. During requirements modeling, analysts tukr:n Thr: Part of the models that use a standard language called busine. process modeling notationtss, and workflows. tz ,IIPMN). IIPMN includes various shapes and symbols to represent events. Pr. Und The metl-des4 is in and reqt, case met