Running head: SYSTEMS ANALYSIS AND DESIGN
Unit 6 Assignment 6
Table of Contents
Part 1 3
Part 2 4
Part 3 7
The team is now at the end of this information systems project for the company’s advertising personnel. We have been recently informed that they will be an employment reduction that will affect the systems analysis team and our budget which in turn has affected moral based on Ontha Weyout’s response during the meeting. We have identified that while we do have documentation, there is no consistency in it. A standardized method is in need to consolidate it and make the information understandable ...view middle of the document...
Keeping this approach will save the team time in gathering the remaining data and aligning it with what has already been established. CASE tools also incorporate diagrams for programmers and users to get a picture of how the process should flow and user manuals can incorporate this (Kendall & Kendall, 2011). Not only will this accommodate a potentially non-technical person like David, but it could also help others in future documented additions and revisions.
Psuedocode also has a place in this documentation effort. Al is the newest programmer and member of the team. The knowledge of psuedocode that he brings to the table could result in a phased in documented approach for future releases. The assumptive is that he is familiar with CASE tools but may need additional training from the company’s perspective to gain full knowledge of it. That is where Flo comes in if she is not affected by the employment reduction. Since she is very keen on CASE, she and AL could have a conversation of data exchange to gain a better understand and the benefits of each technique. In turn, they could educate David and Mark in a less technical way to provide them clarity.
Ouvera has presented a concern as a result of the recent forced employment reduction; loss of time. Since we have less staff assigned to handle the final tasks of the original project, we are put in a position to make some adjustments to bring this project to completion. She is also using the group’s PERT diagram as a guide that shows a projected target completion in the month of July for this project. A PERT diagram’s time does not account for unforeseen changes such as a forced employment reduction and can be updated as the project progresses (Picariello, 2010)
Ouvera and Stan feel that eliminating the testing portion at this point would be an acceptable loss versus my suggestion of delaying it and pushing out the completion date. As a systems analyst and project lead, hearing that is a major concern and I would have to seriously consider using them for future projects. I would not remove them from this project as they have brought value to the team in addition to the team not needing more headcount changes as that will continue to affect moral negatively. Testing from the early stages of this project’s lifecycle to even the training portion is very important. The purpose of testing is to identify breakage, reduce defects, and reduce cost as we progress through the project (Kendall & Kendall, 2011). If we do not continue to perform thorough testing at the remaining stages of the project, we risk unforeseen problems arising. This also ensures that our documentation is on track and understandable with our testing initiatives on the program and their associated links. Ouvera and Stan should not discredit testing at this stage because testing for accurate and inaccurate data may find more problems that were not caught in the early stages. Since we have built a...