ITEC-2040 Systems Analysis
|
|
|
|
SDLC Phases: Factory Systems Development Project | |
File Size: | 28 kb |
File Type: | docx |
Excerpt: The “Factory System Development Project” is a high risk high reward systems upgrade (Satzinger, Jackson, & Burd, 2009, p. 69). Sally Jones has an opportunity to increase the overall input/output of the organization through automated streamlining efforts. However, this must be done without drastically interfering with worker production on the factory floor. This means an iterated approach such as a spiral model is not going to work. As such, I would recommend the modified waterfall approach (Satzinger, Jackson, & Burd, 2009, p. 42).
Functional and Non-functional Requirements | |
File Size: | 25 kb |
File Type: | docx |
Excerpt: When a system analyst begins the process of gathering information on a new project, they are essentially looking for requirements of the proposed system, specifically functional and non-functional requirements. That is, what the system will do and how the system should do it (Satzinger, Jackson, & Burd, 2009, p. 123). This means that the analyst must ask questions, delve into the ins and outs of what the current business processes and systems are, which brought about the need for a new system.
Use Cases vs. ERDs | |
File Size: | 21 kb |
File Type: | docx |
Excerpt: Diagrams based on use cases try to model data structures on how people think and interact with systems in the physical world. This means that the high level overview of a system based on a use case diagram is easy to follow and comprehend intuitively. Also, knowing how users and/or customer interact with the system means that functions of the system are more easily apparent. Missing functions can be discovered before it is too late.
Shopping DFD | |
File Size: | 21 kb |
File Type: | docx |
Excerpt: When writing up this DFD, I went through several iterations which were as detailed as I could imagine. From there I began to combine redundant data, and extract unneeded processes. This led me to a dot point outline which consisted of about twenty events, still too large. At this point, I began to think in generalizations, and that is when I realized I was not writing a dataflow, but a process flow (David & Yen, 1998, p. 24.2). With this epiphany, I was able to cut back the processes from twenty down to seven. Even so, I was still left with six primary data stores and a temporary data store, all of which are included in my DFD.
Technical Requirements Weighting Matrix | |
File Size: | 64 kb |
File Type: | docx |
Excerpt: The hardest decision within these weighting requirements was determining the raw values for the in-house build. Being that I do not know anything about the programmers, I cannot give an accurate assessment of their skills. As such, I went off of a rounding solution. Essentially, I took the raw scores for the other two systems, added them together, and divided them by two. This number was then rounded down to the nearest integer.
Comment Box is loading comments...