Expert answer:Need management help with a typical software devel
Answer & Explanation:This project will simulate the process and deliverables for a typical software development project and go through the major steps of the software development life cycle. This will give you real experience in each stage, from planning, requirements gathering, system design, implementation, and testing. You will use UML diagrams, wireframes, text descriptions, and graphs to create your deliverables.I have attached the guidelines for this three part project. 20141215_spring1update2015_mgt5150finalproject.pdfmgt_finalproject.pdf
20141215_spring1update2015_mgt5150finalproject.pdf
mgt_finalproject.pdf
Unformatted Attachment Preview
Final Project (100 points total)
Part I – Week 2
(30 points)
This project will simulate the process and deliverables for a typical software development project and go
through the major steps of the software development life cycle. This will give you real experience in
each stage, from planning, requirements gathering, system design, implementation, and testing. The
point is to develop and describe a project in such a way that it feels “real”, that it presents a system that
could very well exist and provides documentation that all stakeholders could understand and work with.
You will use UML diagrams, wireframes, text descriptions, and graphs to create your deliverables. You
will not be required to develop any code or create a product, only the supporting documentation.
First, select one of the following possible scenarios:
o
o
o
A mobile application that will compete with the latest games on a tablet platform
A website for a bank that allows customers to manage their finances
An air traffic control suite that will be utilized by a major metropolitan airport for
routing and management of airplane traffic
Next, you will create a number of documentation deliverables that will reflect the scenario you chose.
This scenario will be used for Parts 2 and 3 as well. These deliverables will combine together to create
your software development project report. Each deliverable should take a minimum of one page.
Include citations throughout, as necessary. Part I deliverables are as follows:
1. Product Overview
A description of the overall product being developed, along with related information, such as
the market, competitors, and constraints.
Notes: This is written in paragraph form, perhaps with a chart to support your claims if
necessary. Define what you want to build in a very broad sense and why you would want to
build it. Start thinking here about tasks and features that customers and user s expect with this
system.
2. Stakeholder Overview
Identify the stakeholders and their desires. Determine objectives, possible conflicts, and rank
importance of certain aspects (cost, functionality, etc.) to each stakeholder.
Notes: Works best in table format listing each party involved, how much say they have, how
much time they can devote, how critical they are, etc.. You may choose a ranking system for
such things as long as you define it.
3. Requirements Analysis
Create a list of at least ten (10) system requirements.
Notes: Define in very clear, detailed terms what your system does. You will want requirements
that are both functional and non-functional. Requirements may be dependent on other
requirements or grouped into subsets.
Product Overview
10 points
Stakeholders
10 points
Requirements Analysis 10 points
Grading Rubric:
The following is a list of the categories and specifics for the documentation you will be graded on. This
applies to each deliverable and the project as a whole. Your documentation should be consistent across
each individual deliverables and across all 3 parts. For example, if you create a requirement, be sure to
include a portion of the design that reflects it and a use case that checks it.
Ideal documentation rubric:
Diagrams
Easy to follow
Uses standard diagram conventions
Uses different levels of abstraction to present information
Complete and consistent with system overview
Spelling and Grammar
No spelling errors
No grammatical errors
Structure and Coherence
Paragraphs are developed and flow together, include strong topic sentences
Paragraphs demonstrate unity with the chosen topic
Sections and headings are clear and organized
Subsections used to organize material
Introductions define individual deliverables and their purpose
Clarity
Vocabulary used correctly and precisely
Overall Appearance
Documentation is complete, accurate, and consistent with overall project
No formatting errors
Tables and figures include captions
Part II – Week 5
(40 points)
Continue developing deliverables using the scenario you chose in Part I. Each deliverable should take a
minimum of one page. Include citations throughout, as necessary. Part II deliverables are as follows:
1. Risk Assessment
Create a risk assessment that lists risks along with severity and probability.
Notes: Table of all the possible things that could go wrong, be it internal or external to the
program. Like stakeholders, you will want to rank them and provide a definition for how you
prioritize them
2. System Overview
Define the system architecture and what components will be developed. Identify functional
elements in your system architecture and link your requirements to them.
Notes: The system overview and design show how you will create your system. There should be
a clear link to requirements, but the system overview can go further by defining what your
system looks like behind the scenes.
3. Schedule/Process Overview
Define the process life cycle that should be implemented (for example, Agile). Identify who and
how many people should be tasked for each phase.
Notes: Provide a Gantt chart with possible time values and personnel that mirror the different
components and modules you outline in the system overview/design.
Risk Assessment
10 points
System Overview
15 points
Schedule/Process Overview 15 points
Grading Rubric:
The following is a list of the categories and specifics for the documentation you will be graded on. This
applies to each deliverable and the project as a whole. Your documentation should be consistent across
each individual deliverables and across all 3 parts. For example, if you create a requirement, be sure to
include a portion of the design that reflects it and a use case that checks it.
Ideal documentation rubric:
Diagrams
Easy to follow
Uses standard diagram conventions
Uses different levels of abstraction to present information
Complete and consistent with system overview
Spelling and Grammar
No spelling errors
No grammatical errors
Structure and Coherence
Paragraphs are developed and flow together, include strong topic sentences
Paragraphs demonstrate unity with the chosen topic
Sections and headings are clear and organized
Subsections used to organize material
Introductions define individual deliverables and their purpose
Clarity
Vocabulary used correctly and precisely
Overall Appearance
Documentation is complete, accurate, and consistent with overall project
No formatting errors
Tables and figures include captions
Part III – Week 7
(30 points)
Continue developing deliverables using the scenario you chose in Part I. Each deliverable should take a
minimum of one page. Include citations throughout, as necessary. Part III deliverables are as follows:
1. System Design
Create a UML diagram that illustrates the major components of the system and how they relate
to one another. (You can use PowerPoint, Visio, or an approved graphics program to create
this.)
Notes: Graphic representation of what you state in the overview. At a minimum, use UML to
display the major components of your system (software, hardware, users, etc…) and how it all
interconnects. Consider expanding further to include a diagram of what information is collected
from each module, or perhaps a state chart for the user as they access your system.
2. Wireframe Prototype
Create a visual wireframe prototype of what your software might look like. You can use
PowerPoint, Visio, or any approved graphics program to create a wireframe. For more tools on
wireframing, check out http://webdesignledger.com/tools/10-excellent-tools-for-creating-webdesign-wireframes.
3. Testing Plan
Create a testing plan that highlights what elements will be tested and how they will be tested.
Identify critical components that need the most focus. Include at least four use cases that
illustrate steps taken to perform a basic test.
System Design (UML Diagram) 10 points
Wireframe Prototype
10 points
Testing Plan
10 points
Grading Rubric:
The following is a list of the categories and specifics for the documentation you will be graded on. This
applies to each deliverable and the project as a whole. Your documentation should be consistent across
each individual deliverables and across all 3 parts. For example, if you create a requirement, be sure to
include a portion of the design that reflects it and a use case that checks it.
Ideal documentation rubric:
Diagrams
Easy to follow
Uses standard diagram conventions
Uses different levels of abstraction to present information
Complete and consistent with system overview
Spelling and Grammar
No spelling errors
No grammatical errors
Structure and Coherence
Paragraphs are developed and flow together, include strong topic sentences
Paragraphs demonstrate unity with the chosen topic
Sections and headings are clear and organized
Subsections used to organize material
Introductions define individual deliverables and their purpose
Clarity
Vocabulary used correctly and precisely
Overall Appearance
Documentation is complete, accurate, and consistent with overall project
No formatting errors
Tables and figures include captions
Final Project (100 points total)
Part I – Week 2
(30 points)
This project will simulate the process and deliverables for a typical software development project and go
through the major steps of the software development life cycle. This will give you real experience in
each stage, from planning, requirements gathering, system design, implementation, and testing. The
point is to develop and describe a project in such a way that it feels “real”, that it presents a system that
could very well exist and provides documentation that all stakeholders could understand and work with.
You will use UML diagrams, wireframes, text descriptions, and graphs to create your deliverables. You
will not be required to develop any code or create a product, only the supporting documentation.
First, select one of the following possible scenarios:
o
o
o
A mobile application that will compete with the latest games on a tablet platform
A website for a bank that allows customers to manage their finances
An air traffic control suite that will be utilized by a major metropolitan airport for
routing and management of airplane traffic
Next, you will create a number of documentation deliverables that will reflect the scenario you chose.
This scenario will be used for Parts 2 and 3 as well. These deliverables will combine together to create
your software development project report. Each deliverable should take a minimum of one page.
Include citations throughout, as necessary. Part I deliverables are as follows:
1. Product Overview
A description of the overall product being developed, along with related information, such as
the market, competitors, and constraints.
Notes: This is written in paragraph form, perhaps with a chart to support your claims if
necessary. Define what you want to build in a very broad sense and why you would want to
build it. Start thinking here about tasks and features that customers and user s expect with this
system.
2. Stakeholder Overview
Identify the stakeholders and their desires. Determine objectives, possible conflicts, and rank
importance of certain aspects (cost, functionality, etc.) to each stakeholder.
Notes: Works best in table format listing each party involved, how much say they have, how
much time they can devote, how critical they are, etc.. You may choose a ranking system for
such things as long as you define it.
3. Requirements Analysis
Create a list of at least ten (10) system requirements.
Notes: Define in very clear, detailed terms what your system does. You will want requirements
that are both functional and non-functional. Requirements may be dependent on other
requirements or grouped into subsets.
Product Overview
10 points
Stakeholders
10 points
Requirements Analysis 10 points
Grading Rubric:
The following is a list of the categories and specifics for the documentation you will be graded on. This
applies to each deliverable and the project as a whole. Your documentation should be consistent across
each individual deliverables and across all 3 parts. For example, if you create a requirement, be sure to
include a portion of the design that reflects it and a use case that checks it.
Ideal documentation rubric:
Diagrams
Easy to follow
Uses standard diagram conventions
Uses different levels of abstraction to present information
Complete and consistent with system overview
Spelling and Grammar
No spelling errors
No grammatical errors
Structure and Coherence
Paragraphs are developed and flow together, include strong topic sentences
Paragraphs demonstrate unity with the chosen topic
Sections and headings are clear and organized
Subsections used to organize material
Introductions define individual deliverables and their purpose
Clarity
Vocabulary used correctly and precisely
Overall Appearance
Documentation is complete, accurate, and consistent with overall project
No formatting errors
Tables and figures include captions
Part II – Week 5
(40 points)
Continue developing deliverables using the scenario you chose in Part I. Each deliverable should take a
minimum of one page. Include citations throughout, as necessary. Part II deliverables are as follows:
1. Risk Assessment
Create a risk assessment that lists risks along with severity and probability.
Notes: Table of all the possible things that could go wrong, be it internal or external to the
program. Like stakeholders, you will want to rank them and provide a definition for how you
prioritize them
2. System Overview
Define the system architecture and what components will be developed. Identify functional
elements in your system architecture and link your requirements to them.
Notes: The system overview and design show how you will create your system. There should be
a clear link to requirements, but the system overview can go further by defining what your
system looks like behind the scenes.
3. Schedule/Process Overview
Define the process life cycle that should be implemented (for example, Agile). Identify who and
how many people should be tasked for each phase.
Notes: Provide a Gantt chart with possible time values and personnel that mirror the different
components and modules you outline in the system overview/design.
Risk Assessment
10 points
System Overview
15 points
Schedule/Process Overview 15 points
Grading Rubric:
The following is a list of the categories and specifics for the documentation you will be graded on. This
applies to each deliverable and the project as a whole. Your documentation should be consistent across
each individual deliverables and across all 3 parts. For example, if you create a requirement, be sure to
include a portion of the design that reflects it and a use case that checks it.
Ideal documentation rubric:
Diagrams
Easy to follow
Uses standard diagram conventions
Uses different levels of abstraction to present information
Complete and consistent with system overview
Spelling and Grammar
No spelling errors
No grammatical errors
Structure and Coherence
Paragraphs are developed and flow together, include strong topic sentences
Paragraphs demonstrate unity with the chosen topic
Sections and headings are clear and organized
Subsections used to organize material
Introductions define individual deliverables and their purpose
Clarity
Vocabulary used correctly and precisely
Overall Appearance
Documentation is complete, accurate, and consistent with overall project
No formatting errors
Tables and figures include captions
Part III – Week 7
(30 points)
Continue developing deliverables using the scenario you chose in Part I. Each deliverable should take a
minimum of one page. Include citations throughout, as necessary. Part III deliverables are as follows:
1. System Design
Create a UML diagram that illustrates the major components of the system and how they relate
to one another. (You can use PowerPoint, Visio, or an approved graphics program to create
this.)
Notes: Graphic representation of what you state in the overview. At a minimum, use UML to
display the major components of your system (software, hardware, users, etc…) and how it all
interconnects. Consider expanding further to include a diagram of what information is collected
from each module, or perhaps a state chart for the user as they access your system.
2. Wireframe Prototype
Create a visual wireframe prototype of what your software might look like. You can use
PowerPoint, Visio, or any approved graphics program to create a wireframe. For more tools on
wireframing, check out http://webdesignledger.com/tools/10-excellent-tools-for-creating-webdesign-wireframes.
3. Testing Plan
Create a testing plan that highlights what elements will be tested and how they will be tested.
Identify critical components that need the most focus. Include at least four use cases that
illustrate steps taken to perform a basic test.
System Design (UML Diagram) 10 points
Wireframe Prototype
10 points
Testing Plan
10 points
Grading Rubric:
The following is a list of the categories and specifics for the documentation you will be graded on. This
applies to each deliverable and the project as a whole. Your documentation should be consistent across
each individual deliverables and across all 3 parts. For example, if you create a requirement, be sure to
include a portion of the design that reflects it and a use case that checks it.
Ideal documentation rubric:
Diagrams
Easy to follow
Uses standard diagram conventions
Uses different levels of abstraction to present information
Complete and consistent with system overview
Spelling and Grammar
No spelling errors
No grammatical errors
Structure and Coherence
Paragraphs are developed and flow together, include strong topic sentences
Paragraphs demonstrate unity with the chosen topic
Sections and headings are clear and organized
Subsections used to organize material
Introductions define individual deliverables and their purpose
Clarity
Vocabulary used correctly and precisely
Overall Appearance
Documentation is complete, accurate, and consistent with overall project
No formatting errors
Tables and figures include captions
…
Purchase answer to see full
attachment
How it works
- Paste your instructions in the instructions box. You can also attach an instructions file
- Select the writer category, deadline, education level and review the instructions
- Make a payment for the order to be assignment to a writer
- Download the paper after the writer uploads it
Will the writer plagiarize my essay?
You will get a plagiarism-free paper and you can get an originality report upon request.
Is this service safe?
All the personal information is confidential and we have 100% safe payment methods. We also guarantee good grades