Watch the Lynda.com video, "Insights on Software Quality Engineering."
Think of a software application (for example, a time tracking application) that you would like to put in for your past or present organization, or an organization that you have read about.
Use the table below to describe as clearly as you can, the specific artifacts in each phase, and an example of how the artifact would look like. Phases
Artifacts
Inception
Name of Artifact: Business case plans
Content: Will explain the project the main idea. It will be who, what when where and why of the project.
Example: There will be a new time tracking system. It will be implemented for the whole company and will go into effect by January 2016. The old time tracking system is really old and needs to be updated to something more user friendly.
Name of Artifact: Risk Table
Content: The main purpose of the risk table is to document and list all risk involved with the project. It will be a able listing all the risk and will then go into detail on how each risk will affect the company
Example:
Risk
Affect
Time off Request
Might not transfer to new time system making it difficult for manager to approve
Operating Systems
Needs to be compatible with current computers so employees can input time
Planning
Name of Artifact: Project Schedule
Content: Will list the main milestones in the project and day which they should be completes
Example:
Stage
Due Date
Coding
Due: July 30, 2015
Testing
Due: Aug 30,2015
Name of Artifact: Work Breakdown Structure
Content: It will breakdown the different task that needs to be done and who will perform the task
Example:
Task
Name
Risk Assessment
Kyler Polk
Business Plan
William Robertson
Project Schedule
Le Hampton
Name of Artifact: Financial Plans/Project Cost
Content: This will be the list of all the funds available to implement the project. It will also