Type: Individual ProjectUnit: Software Engineering IssuesDue Date: Mon, 9/19/16Grading Type: NumericPoints Possible: 250Points Earned: 0Deliverable Length: 3 –4 new pages in the Software Engineering Research Document, Microsoft Word document Assignment DescriptionWeekly tasks or assignments (Individual or Group Projects) will be due by Monday and late submissions will be assigned a late penalty in accordance with the late penalty policy found in the syllabus. NOTE: All submission posting times are based on midnight Central Time.Key AssignmentThe final step in developing the Software Engineering Research document is to examine Software Engineering practices related to verification, validation, operations, maintenance, logistics support, retirement, and disposal of software. These key areas of Software Engineering are vital to successful software development projects and should be well understood in advance of the planning for any software development project. Your goal in this stage of the overall project is to identify how software engineering practices can improve each of these areas of Software Engineering. You will also further refine the Software Engineering Research document to produce the Final Draft version. Updates may be based on peer and instructor feedback.The project deliverables are:Update the Software Engineering Research document title page with new date and project name.Update previously completed sections based on instructor feedback.Software Engineering Issues:Highlight the following key issues and discuss how Software Engineering practices can be applied to improve the projects and reduce risks:VerificationValidationOperationsMaintenanceLogistics SupportRetirementDisposalFor each issue, describe at least one Software Engineering principle or practice that could be applied, the specific activity it applies to, and the effect it would have.Examples would be appropriate.Software Engineering Research Document Final Version:Review the entire document for any changes and improvements you would like to make.Ensure this final version of the plan is sufficiently detailed to allow the organization to confidently move forward with software engineering projects based on your findings.Any previous instructor feedback should be addressed with appropriate changes.Be sure to update your table of contents before submission.Name the document yourname_SWE311_IP5.docSubmit the document for gradingPlease submit your assignment.
phillip_isiah_houston_sr_swe311_ip4.doc
Unformatted Attachment Preview
Course Name
The Software Engineering Profession
{SWE311 – 1603B – 02}
Course Number
Unit 4 Individual Project
Project Name
Improvement of the CTU intellipath™.
Student Name
Phillip Isiah Houston Sr.
Instructor Name
Jeffrey Hedrington
Date
Monday 12 September 2016
Table of Contents
CHAPTER 1 ……………………………………………………………………………………………………………………………………. 3
Introduction ………………………………………………………………………………………………………………………………….3
Organization Background……………………………………………………………………………………………………………….3
Problem Statement ………………………………………………………………………………………………………………………..4
CHAPTER TWO ………………………………………………………………………………………………………………………………. 5
Goals/Objectives …………………………………………………………………………………………………………………………..5
Procedures/Scope of Work ……………………………………………………………………………………………………………..5
Timetable ……………………………………………………………………………………………………………………………………..5
Budget …………………………………………………………………………………………………………………………………………6
Key Personnel……………………………………………………………………………………………………………………………….6
Evaluation…………………………………………………………………………………………………………………………………….6
Software engineering standards……………………………………………………………………………………………………….7
Software Engineering Communications ………………………………………………………………………………………….11
Software Engineering Ethics …………………………………………………………………………………………………………14
CHAPTER THREE …………………………………………………………………………………………………………………………… 18
Methodology ………………………………………………………………………………………………………………………………18
Introduction ………………………………………………………………………………………………………………………………..18
Research Design ………………………………………………………………………………………………………………………….18
Questionnaire………………………………………………………………………………………………………………………………19
Appendix ……………………………………………………………………………………………………………………………………20
CHAPTER 1
Introduction
Colorado Technical University (CTU) is a United States for-profit university. It was founded in the
year 1965. The university offers courses for undergraduate, graduate, doctoral degrees primarily in
management, business, and technology. The school had been established in 1965 as Colorado
Technical College with the focus of training former militaries personnel in vocational and technical
subjects. In the same year, the institution gained university status and its name changed from
Colorado Technical College to Colorado Technical University.
It is has been recognized as Center of Academic Excellence in Information Assurance Education by
both the Department of Homeland Security and the NSA. CTU is said to have not less than 70,000
graduates worldwide according to the Colorado Tech analysis.
Organization Background
Colorado Technical University was established half a century ago and so far it has
helped many students achieve dreams by equipping them with the knowledge
required in the industries. It has been providing degree programs, relevant to the
industry thus providing employers with well-educated workforce. The university
continues to innovate certain areas such as adaptive learning leveraging technology,
problem based areas their well dedicated staff and faculties.
CTU have also established itself as a leader of online and hybrid learning. It was
named the *Best of Best* in the year 2009 i.e. 9 years after implementation of the
online degree programs.
In 2013, CTU Online MBA was among the ranked top 10 world Online MBA
programs and hence received another great honor. Their commitments to innovative
technology lead to creation of M.U.S.E (My Unique Student Experience). This made
the CTU receive the Association of Private Sector Colleges and Universities award
in recognition of advantages provided to students online.
Problem Statement
Based on the previous researches I have done the CTU Intellipath™ (online software
offered by CTU for personalized learning) needs to be addressed. Its purpose is
doing away with the one-size-fits-all approach to education by ensuring the students
are provided with their own personalized learning path.
Currently, in the CTU Student & Graduate Reviews the Intellipath™ is claimed to
give wrong answers to students who ends up failing. I have also noticed that the
software doesn’t offer all the required courses for the students.
This problem has been continuously reported for about one year but it seems no
solution has been found thus calling for my interest to research on how to improve
the system. Finding the solution to the problem will be of great help to the student
get correct answers and safe the time and money wasted in repeating the cause in
cases of failure.
CHAPTER TWO
Goals/Objectives
•
To ensure that student receives correct answers
•
To ensure that no student repeats the course for being failed by the software
•
To ensure that records for students studying online are kept safe
Procedures/Scope of Work
Learn and understand the system is implemented and how it works so as to get a
clear understanding of what results to all the problems being reported. This will
activities such visiting the developers of the system, testing the system and doing the
actual improvement and debugging of the system.
Timetable
Project Gantt chart:
ACTIVITY
1. Design and implement
research program for the
project
1.1. Conduct needs
assessment
1.2. Design training
modules
1.3. Conduct training
2. Improve procedure for
project management
2.1. Conduct management
audit of current
Procedures
IMPLEMENTATION TIME
Week1
Week 2 Week
3
Week 4
RESPONSIBILIT
Y
Week 5
Program
Manager (PM)
Consultant
Consultant
Consultant
Program
Manager
Consultant
Budget
Costs and Budget
Description of Work
Research on the overall development of
the system.
Get the necessary software and experts
to work with to debug the system.
Test the system with real users and ask
them to comment on its functionality as
compared to the other system.
Total
Phase One
Phase Two
Phase Three
Start and End Dates
$100.00
$250.00
$80.00
$ 430.00
Key Personnel
Though not limited, these are the personnel who will begin the proposed project
research.
Client
Sponsor
Project manager
Team
Thomas
James
Phillip
Thomas, James, Phillip
Evaluation
Each project progress plan will be recorded on a Gantt chat. The Gantt chat will have
a combination of Project task and time periods.
For proper execution of all activities, each component will be achieved as planned
before reaching the objectives. After receiving the components, the objectives will
then be achieved and will be a major contribution to the project goals.
These progresses will be recorded by the project manager thought the project.
Software engineering standards.
According to ISO 1997, Standards refers to documented agreements that contains technical
specifications which are used consistently as rules, definitions or guidelines of characteristics. All
these ensures that products, materials, services and processes fits their purpose. These standards
provides rules, heuristics and guidelines which are to be followed in order to achieve assurance of
good practice.
Below are some of the standards that am going to use in order to achieve the goals of my
projects?
i. IEEE Std 730: In this standard, legal liability is its basic rationale. It is mainly directed
towards development and maintenance of critical software I.e. Where failure could
affect safety of the system or cause social/financial losses. It’s oriented towards
delineating the planned systematic actions on the project involved, this provides enough
confidence that the software project involved meets the established technical
requirements. This standard establishes the required minimum contents and all the
required format for quality assurance plans in software development.
ii. Draft IEEE Std 1061: This is a standard that provides methodology for establishing quality
requirements and identifying, implementing, analyzing, and validating the product and
process of software quality measurements. It should be noted that these standard do not
prescribe any specific metrics but it includes examples of metrics with complete
example of the standard’s use.
This standard does not prescribe specific metrics. It does include examples of metrics
together with a complete example of the standard’s use.
iii. IEEE Std 1045: This standard gives the framework of measuring and reporting the
productivity of software processes. Its main focus is the definition of how software
productivity is measured and what will be reported when productivity results are given.
The standard is mainly meant for users who want to measure the software process
productivity for code creation and products documentations.
These standards will assist in:
i. Creating a powerful organization.
Having applied all the above standards, they will assist in setting a powerful organization and
marketing tools regardless of its size. These standards will also assist in fine tuning the performance
and manage all the risks that are being faced by the organization while operating in a sustainable
and efficient way. They will allow users to demonstrate the quality of what they do to their
customers, and also see how to best practices into the organization.
ii. Improving the organization performance.
Standards gives users the knowledge required to fine-tune the organization in order to provide the
best in performance. The results of these are; increased profits and tangible growth. Organizations
using these standards have more potential customers, better cost control and more efficient ways of
working hence are able to implement more efficient working practices.
iii. Reducing organizations’ risks.
These standard will reduce the organizations risks such as; IT security breaches, loss of students
which may cripple the organization and may take long or may never recover. They will prepare the
organization so that many threats some of which they may never have considered will be so far or
less likely to hit the organization, they can also turn on more opportunities.
How the standards used in this project affects software engineering processes.
Software engineering process is a structure imposed on the software development when developing
a software product. The structure is usually presented by work phases which are applied to the
build of a software product.
The above standards will affect Engineering processes in various ways. For example, having
applied the second standard (Draft IEEE Std 1061); it will be mandatory that software specification
must define the functionality of the software and also the software constraints. This standard will
also ensure that the software design and implementation produces a software that meets all the
specifications.
The first standard i.e. IEEE Std 730, will affect the software evolution process by the software
continues to evolve throughout the development and maintenance process in order to meet the
changing customers’ needs. All these will be done on a critical software as per the standard.
The third standard (IEEE Std 1045) will affect both the Software evolution and Software validation
process. The standard is mainly concerned with the productivity of the software process. For the
software to be productive for the customer, it must meet all the functionalities specified by the
customer in order to make it easier to use thus reducing time spent for a given task. Old and
outdated software will also result to low productivity thus the software need to continuously evolve
to meet the changing customer requirement.
Top-level plan for implementing the Software Engineering standards.
The top level plan refers to projecting how the system will be implemented to meet all the
requirements with very few acceptable risks or none. The main reason for developing this top-level
plan is to technical foundation for the program being planned for.
At the beginning of the plan, a MITRE system engineer (SE) will be involved to establish a sound
program baseline. These includes the technical requirements, understanding of system operational
requirements, the architecture, system design concept and the cost and schedule for the program.
In these situations, the Software Engineer will be expected to:
i. Understand the role and purpose of top-level system plan in acquisition process.
ii. Understand when and how to undertake the top-level system plan.
iii. Understand the benefits and risks associated.
iv. Identifying and engaging with the subject matter experts (SMEs) who have the appropriate
technical skills needed for developing top-level plan.
v. Finally apply what has been learnt in the design activity in program planning activities.
Software Engineering Communications
The following information are necessary to support the software engineering
projects.
Techniques and communication skills required: Communication is very important
in software project. Any project whether handled by cross department or dedicated
project team depends on crucial techniques and communication skills that are set in
order for the project to succeed.
Good human interaction and communication: IT manager should be aware that
the way human being interact and communicate during the software project
development may either result to success or failure. By ensuring good
communication between stakeholders of the project will increase the chances of
project success.
Understand what project communication is: Every project member involved
should understand that project communication refers to specific techniques and
behaviors which are used to lead, motivate, delegate and give feedback to
stakeholders who are working on the project.
To describe the communication flow of the information described above, we will use
the three channels that are used by project managers during the start of the project.
These channels are continuously managed and improved to increase the chances of
project success.
To ensure effective plan in this project, the plan must;
Ease the process of updating stakeholders: Frequent communications
ensures that stakeholders are kept in the loop.
Should be used all through in the software development process: From
the definition of software requirement, the plan assists in informing the
stakeholders the communication channels to be used on the project. It also
informs them who should report to whom, type, frequency, and the project
meeting format.
Should facilitate team development: Good communication ensures proper
teamwork where every objective and tasks to be completed are understood
clearly by all team members.
Saves the creation of additional documentation: When effective
communication steps are taken from the beginning of the project, project
documentation is greatly reduced.
The tools necessary to support these processes are;
i.
Email: Allows communication of project teams in form of text, video, and
audio files.
ii.
Instant messaging (IM): Allows real time communication between team
members.
iii.
Interoffice memos: Allows for formal forum for communication policies,
key dates, and procedures.
iv.
Telephone/video conferences: It is a medium that involves all team
members including the ones located in other geographic regions.
v.
Project status meetings: It allows for project reviews and regular status
updates.
vi.
Intranet and internet boards: These tools formally communicates status,
highlights, progress and objectives to all.
vii.
Project road show: It is a tool for providing feedback to users and
stakeholders.
viii.
Walk-about: This involves meting the clients with your team and approach
them face to face.
Software Engineering Ethics
Role of Software Engineer and professional ethics embraced by Software Engineering
discipline.
Software engineering ethics refers to the engineering ethics subset that are applied when
designing and developing software systems. Engineering philosophy and ethics looks at the
relationship between the individual engineer, his or her employer, client, and the whole
society.
The first role of software engineer in software engineering is to apply computer science
principles, techniques and mathematical analysis in the systems development life cycle
(SDLC) i.e. to the design, development, testing and software evaluation and systems which
enables the computers perform their applications.
Software engineers are also involved in designing and developing of various types of
software for compilers and operating systems, and for network distribution. It is the duty of
computer engineers in programming to instruct the computer how to perform its work, this
is done with the help of line by line commands which dictates the computer functions. They
therefore must possess strong skills in programming but their concern should be mainly in
developing algorithms, analyzing, and solving problems associated with programming other
than writing the codes.
Software engineers who are responsible for developing or working on a certain application
must first analyze the users’ needs. After analyzing the needs, they then do the designing,
construction, testing and maintenance of the computer applications system or software to
meet the needs.
It is also the role of software engineers to coordinate how the company’s plan for future
growth and computer systems used are constructed and maintained. They coordinate all the
company’s department’s computer needs e.g. orders, Inventories, billings, payrolls
recordkeeping, and making suggestions on the appropriate technical directions. It is also the
role of the engineers to set up the organization intranets i.e. the network that links the
organization computers to enhance communication among the departments.
Software engineers also configures, implements and installs the complete computer system
for the organization. They participate in providing support to the organization customers.
Selling of complex computer systems requires some customization for the organization
purchasing the system, it is therefore the role of software engineers to explain the
requirements for instating the new system in the organization computing environment. It is
their role to ensure proper security of the system they are installing and configuring.
Some Professional ethics embraced by Software Engineering discipline are:
Software enginee …
Purchase answer to see full
attachment
Recent Comments