ArielJoseph_IT425_IP5 - 1 This task was originally...

Info icon This preview shows pages 1–5. Sign up to view the full content.

View Full Document Right Arrow Icon
1 This task was originally submitted during the [1701A] in [IT425] with [Brandon DeLeeuw] . System Analysis, Design, and Integration IT425 Software Development Life Cycle Ariel Joseph 05/10/2017
Image of page 1

Info icon This preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
2 Contents System Overview ......................................................................................................................................... 3 Requirements Specifications .................................................................................................................... 4 System Design .............................................................................................................................................. 6 CASE Designs ........................................................................................................................................... 6 Test and Quality Assurance Plan ................................................................................................................ 12 Testing & Quality Assurance .................................................................................................................. 12 Development Strategy ............................................................................................................................... 16 Proposal ................................................................................................................................................. 16 Integration and Deployment Plan .............................................................................................................. 18 Work Breakdown Structure ................................................................................................................... 18
Image of page 2
3 System Overview This project will show the processes that are required to complete a system development life cycle (SDLC) for the creation of a specific software application. This application is being designed for a project management firm to allow employees to log the amount of time they have worked on each individual project and allow managers to approve time sheets. This firm is small and just needs basic functionality. With as much work as they manage they want it to be user friendly and not complicated with unnecessary functions. The intention of this application is to provide a simple interface for employees to log their time worked and for managers to be able to approve or deny the time sheet submissions and also post projects available to be worked. The system will also allow managers to run reports to see which projects have the most people working on them and the ones that have not been touched at all within a certain number of days since project commencement. All office employees, managers, and partners of the firm will be the primary users of this application. Other authorized user to update and maintain the servers will also have access. The main purpose for this is to allow managers to see where their projects stand in real time daily and for employees to get their time inputted quickly and accurately. The stakeholders of this application will be focused mainly on office staff and management. The project will be sponsored by the owner of the firm. .
Image of page 3

Info icon This preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
4 Requirements Specifications The system requirements for this software will be obtained from the end users. Surveying the office staff will allow for getting a feel of what exactly user friendly and efficient means to this firm. After gaining requirements and setting a realistic project completion timeline, development will begin to work on mockups and prototypes. As the project continues we will have another survey session to see what the firm thinks so far and if any additions or subtractions need to take place. We will then begin to build and do portion check to ensure functionality. The primary functional requirements of this software will come from the interaction between the user and the graphical user interface (GUI) that the software will use. Those requirements are employees being able to view projects available to be worked on and heir description, log time worked on those projects chosen and submit those times to their manager for approval. Managers will see the same interface but with more options for running reports on projects and also getting the functionality to approve or deny time sheets. The GUI will have a
Image of page 4
Image of page 5
This is the end of the preview. Sign up to access the rest of the document.

{[ snackBarMessage ]}

What students are saying

  • Left Quote Icon

    As a current student on this bumpy collegiate pathway, I stumbled upon Course Hero, where I can find study resources for nearly all my courses, get online help from tutors 24/7, and even share my old projects, papers, and lecture notes with other students.

    Student Picture

    Kiran Temple University Fox School of Business ‘17, Course Hero Intern

  • Left Quote Icon

    I cannot even describe how much Course Hero helped me this summer. It’s truly become something I can always rely on and help me. In the end, I was not only able to survive summer classes, but I was able to thrive thanks to Course Hero.

    Student Picture

    Dana University of Pennsylvania ‘17, Course Hero Intern

  • Left Quote Icon

    The ability to access any university’s resources through Course Hero proved invaluable in my case. I was behind on Tulane coursework and actually used UCLA’s materials to help me move forward and get everything together on time.

    Student Picture

    Jill Tulane University ‘16, Course Hero Intern