Type: Individual Project Unit: Quality Assurance Principles Due Date: Wed, 4/12/17 Grading Type: Numeric Points Possible: 100 Points Earned: 0 Deliverable Length: Word document of 10 pages (including empty sections), 600–900 words View objectives for this assignment Overview As you have already learned in your Discussion Board this week, quality assurance in any project might be the most important but overlooked aspect of a project. Lack of quality management, however, can cause an entire project to fail if the final project deliverables do not meet customer expectations and standards. Implementing quality assurance throughout the project improves overall performance of tasks and minimizes the risk of nonacceptance at the end of the project. In this course, you are asked to develop a Quality Management Integration Plan that allows you to select and integrate quality management tools, models, and techniques in the overall performance of the project. You will select a project that you may have developed in a previous class or a known project in an organization to create this plan for. Throughout this course, you will be working on developing several components of final Key Assignment. Additional information and the deliverables for each Individual Project will be provided in the assignment description for this project. In this first Individual Project, you are asked to develop the outline of the sections that will be included in the Quality Management Integration Plan document and a draft of a proposal to submit to your instructor. The other information you will include is a high-level description of the project that you will be developing a quality implementation strategy for. You will also be setting up the Final Key Assignment outline that you will add to each week. The combined Individual Project (IP) assignments will be your final Key Assignment deliverable. Project Selection The first step will be to select a project that you to develop a Quality Management Integration Plan for. This project will be used as the basis for each of the assignments throughout the course and should conform to the following guidelines: 1. 2. Nontrivial: The selected project candidate should reflect a real-life project. Domain knowledge: You will be applying knowledge of this project to address assignments related to quality management, integration, and performance. Select a project that fits these requirements, and submit your proposal to your instructor before proceeding further with the assignments in the course. Approval should be sought within the first few days of the course. Your instructor will tell you how to submit this proposal and what notification will be given for project approval. Assignment Your first task in this process will be to select a project to use as the basis of your Key Assignment. You will also create the shell document for the final project Key Assignment document deliverable that you will be working on throughout the course. As you proceed through each project phase, you will add content to each section of the final document to progressively complete the final project delivery which is the Quality Management Integration Plan. The project deliverables are as follows: • • Submit the project proposal to your instructor for approval Quality Management Integration Plan o Use Word o Title page ▪ Course number and name ▪ Project name ▪ Your name ▪ Date o Table of Contents (TOC) ▪ Use an autogenerated TOC. ▪ This should be on a separate page. ▪ This should be a maximum of 3 levels deep. ▪ Be sure to update the fields of the TOC so that it is up-to-date before submitting your project. o Section Headings (create each heading on a new page with “TBD” as content, except for Week 1) ▪ Week 1: Project Outline ▪ Week 1: Organizational Readiness for Quality Management ▪ Week 1: Quality Systems Analysis ▪ Week 2: Quality Dimensions and Criteria ▪ Week 3: Quality Process Improvement Tools and Techniques ▪ Week 4: Quality Performance Monitoring and Control ▪ Week 5: Three Levels of Quality Management ▪ Week 5: Quality Performance Communication Plan Create the following sections for Week 1: • • • • Project Outline o Include a brief description of the project. o Describe the overall project deliverables. o Material can be taken from the approved proposal that you submitted to the instructor. This may serve as the draft for the proposal. o Be sure that this project is approved by the instructor. Organizational Readiness for Quality Management o Discuss which quality systems the organization employs today. o Discuss the organization's readiness to incorporate in the selected project. o Include additional support that might be required to incorporate quality management (e.g., a knowledgeable quality champion). Quality Systems Analysis o Discuss the pros and cons of at least 3 quality systems (e.g., ISO 9000, Six Sigma, plan-do-checkact or plan-do-study-act, capability maturity model integration [CMMI], organizational project management maturity model [OPM3], Malcolm Baldrige). o Identify which one or combination is most appropriate for this project, and discuss why. Name the document "LastName_FirstName_MPM357_IP1.doc." Course Name MPM357 Project Performance and Quality Assurance (MPM 357 – 1702A – 01) Course Number Unit 1 Individual Project Project Name Improvement of the CTU Intellipath™. Student Name Phillip I. Houston Sr. Instructor Name Kay Crook Due Date 12 April 2017 Table of Contents Week 1: Project Outline ................................................................................................................................ 3 Week 1: Organizational Readiness for Quality Management ........................ Error! Bookmark not defined. Week 1: Quality Systems Analysis................................................................................................................ 4 Week 2: Quality Dimensions and Criteria .................................................................................................... 5 Week 3: Quality Process Improvement Tools and Techniques.................................................................... 6 Week 4: Quality Performance Monitoring and Control ............................................................................... 7 Week 5: Three Levels of Quality Management ............................................................................................ 8 Week 5: Quality Performance Communication Plan ................................................................................... 9 Week 1: Project Outline Week 1: Quality Systems Analysis 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. Week 2: Quality Dimensions and Criteria Week 3: Quality Process Improvement Tools and Techniques Week 4: Quality Performance Monitoring and Control Week 5: Three Levels of Quality Management Week 5: Quality Performance Communication Plan Course Name The Software Engineering Profession {SWE311 – 1603B – 02} Course Number Unit 5 Individual Project Project Name Improvement of the CTU intellipath™. Student Name Phillip Isiah Houston Sr. Instructor Name Jeffrey Hedrington Date Monday 19 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 ............................................................................................................. Error! Bookmark not defined. Key Personnel.................................................................................................................................................6 Evaluation.......................................................................................................................................................6 Software engineering standards......................................................................................................................7 Software Engineering Communications .......................................................................................................11 Software Engineering Ethics ........................................................................................................................14 Software Engineering Issues. .......................................................................................................................18 CHAPTER THREE ............................................................................................................................................. 21 Methodology ................................................................................................................................................21 Introduction ..................................................................................................................................................21 Research Design ...........................................................................................................................................22 Questionnaire................................................................................................................................................22 Appendix ......................................................................................................................................................23 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 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 engineers must act consistently according to the public interest. For example; they must accept full responsibility for the work given and only approve the software once they have ensured it is save, meets users specification and done thorough testing. ➢ Software engineers shall action should meet the clients and employers interests and be consistent with public interest. E.g. They must be honest, provide good service in their area of work, and be straightforward on any limitations of their education and experiences. ➢ Software engineers shall ensure that the product and its modification meets the best standards. I.e. they should strive for higher quality, reasonable schedule, acceptable cost, and ensure that the tradeoff is acceptable by the client and the employers and also the product are available for user and public consideration. Plan for implementation of appropriate software Engineering profession ethics above. In order to successfully implement professional engineering ethics, as a software engineer I will first explain code importance before it is read. This will help every member understand it clearly and even encourage them to hold on it in order to achieve the organization goals. I will then ensure that the project members/ engineers read and understand the CTU mission statement related to this project, i.e. Improvement of the CTU intellipath™. This will give enough reason to the team as to why the codes are important to abide by. They will be printed for the organization to ensure that they are well followed. The ethics shall be sent through the emails to ensure that each member leads and understands it. The email message tone will be that of polite tone and clearly designed to ease understanding of the message. The introduction part will involve thanking the stakeholders for behaving ethically in the past projects. Following the email, we will be conducting a training to all stakeholders on how to follow the ethics. This will be done through discussion on how these ethics affects each stakeholder line of work. The training will be facilitated by supervisors and ethical officers where each stakeholder/member will be issued with a hard copy of these ethics. The final part will involve enforcement of the ethics. This will involve screening the ethics by interviewing the group and comparing the individual answers to the established ethics. It will ensure that each individual has a personal value to that of the project. After describing all the ethics, we will then discuss why the implementation of the ethic will lead to success in the project. Summary of software engineering roles and how to serve the organization. I have learnt that Software engineers basically applies their knowledge, techniques and skills to come up with a system that solves clients’ problems. It’s their duty to ensure that a standard system is delivered to the client within the scheduled time plan and meets all the clients’ requirement. If there is need for explanations of how the system works, the software engineers has that responsibility to explain how the system works and expected outcomes from various inputs. I have also learnt that software engineers face challenges when developing software which requires skills or knowledge that is beyond their education or experience. And as a software engineer, I would be straight forward in explaining to the client about what the software requires other than keeping not meeting the client interest due to lack of necessary skills required. As a software engineer in improving the CTU intellpath, I would take the responsibility of reading the mission statement to the stakeholders and ensure the problem or shortcomings of the system are well understood to each and every stakeholder. I would also explain the system requirement to the Computer engineering of the department in the organization so that when the implementation starts, there will be no time wastage in getting some requirement which might not be available. I would also advocate for ethics establishment and implementation to the organization and the stakeholders of the project. Involving them in the establishment of the ethics will increase the chances of project success as they will feel its value. Software Engineering Issues. Verification Our first issue of discussion is software verification. It refers to the evaluation process in which the intermediary work products of software development lifecycle are evaluated to check if the right track is followed in creating the final product. Intermediary products refers to documents produced during the development phases (specification of requirements, document design, database table design, ER diagrams, traceability matrix, test cases etc.). Mostly we ignore software verification but it should be understood that reviewing the documents can help resolve many potential risks which could have resulted in the later phase of development and can be very costly. It can also be understood as the process of evaluating the software mediator products to ensure that the products satisfies all the conditions specified at the beginning of the phase. Examples includes reviews and walkthrough. Software verification activities. i. Requirement verification involves reviewing all the requirements. ii. Design verification involves reviewing all the design documents with LDD and HLD included. iii. Code review and verification. iv. Document verification for user manuals and related documents. Validation Software validation involves evaluating the final product to ensure the software meets all the business needs. It is the test execution that we do in our day to day life are what is referred as validation activity. Examples includes, functional testing, smoke testing, systems testing and regression testing. The difference between software verification and software validation is that software verification involves evaluation of intermediary products and ensuring that they meet all the specified requirements of that phase. On the other hand, software validation involves evaluating the final product to ensure that it meets the business needs. Another difference is that software verification is done without executing the software while in software validation is done with execution of the software. Software validation activities. i. Test requirements documents preparation, test cases, among other test specifications which analysis the test results. ii. Evaluation to ensure that these test requirements, test cases and all other specifications meets the requirements and is safe to use. iii. Test for boundary values, functionalities and stress. iv. Error messages test and in case and error occurs, the application should terminate gracefully. v. Test to ensure that the software is fit to use and meets the business requirements. Operations This issue can be improved using automated testing practice. Developers who focus on writing quality code them as often as early as possible has their quality infected, a good example is agile software developers. As a result, agile teams often adopt regression testing practice. This is extended to test-first approaches such behavior driven development (BDD) and test driven development (TDD). Since the teams run automated test many times a day, this practice helps them find and fix problems found right away. It thus ensures high quality than other teams who don’t use the practice. It is a good news to operations staff that insists on solution that has sufficient quality approving and releasing their products. Maintenance Software maintenance is a part of SDLC which is widely accepted in our day’s today life. It involves modifying and updating a software product after delivery. There are many reasons which software modification is necessary, some are; Market Conditions, Host Modifications, and Organization Changes among others. Software maintenance activities are: i. Identification & Tracing: involve all the activities pertaining to identifying all the modification or maintenance requirements. ii. Analysis: involves analyzing modification for its impact on the system including security and safety implications. iii. Design: involves designing new modules which need to be replaced or modified. They are designed against requirement specification of the previous stages. iv. Acceptance Testing: the system is tested for acceptance with the users. v. Delivery: involves deploying the software on the target organization after testing its acceptance. Logistics Support Logistics support includes integrated logistics support (ILS), change/configuration management and quality control/ assurance within commercial markets and military. The activities included in this issue are development of the baseline design and plan for change throughout the life cycle, configuration every audit of the software, to systems and vessels, and to equipment. Its impact is measured in terms availability, reliability and maintainability. Retirement Application retirement involves activities of shutting down old and obsolete business applications while still retain access to all the historical data. It can save significant costs resulting from software maintenance of obsolete systems. This practice involves migrating data to an archive store which is accessible independently using some business intelligence organizations tool. It helps the organization reduce hardware, software and resources required for legacy data management. Disposal This refers to the final phase of SDLC that involves disposing a system and closing any contacts in place. When disposing a system, all the information security issues associated should explicitly be addressed. These information becomes obsolete or unusable once they are transferred and thus it is important to ensure protection of government associate information. The key activities associated with system disposal are; Building and executing disposal, Archiving of critical information, media sanitization, and disposal of hardware and software. CHAPTER THREE Methodology Introduction This chapter deals with how the system works and what method of implementation have been used to come up with the system. Data collection and analysis techniques and a detailed explanation of the research method that will be used to realize the objectives of the study. Research Design This study will involve the use of descriptive analysis design. This will involve describing the system, its processes and the data in a clear way, something that will enable presentation of data more meaningfully hence allowing simpler interpretation of the data. It is important to evaluate the current CTU intellipath™ system for the benefit of all the people that are involved both in its development and use. This should involve comparing the CTU intellipath™ with the other intellipath™ which has similar functionality to see how the CTU intellipath can be improved. In analyzing the prototype for group formation, which is the core of this research, very useful results will be obtained. This will give the information that is needed to determine whether the intended objectives of the research have been achieved. This will also assist in identifying the areas that need improvement. Questionnaire This is the main instrument that will be used to collect data for evaluation. The questionnaire will have three sections. The first section will have a set of questions related to the organization use of intellipath™ . This section will collect background data on whether the university have been having problems and how often the system is used for educational purposes. This will confirm that the student are the affected by this problem. The second section will have a set of questions relating to the usability of the prototype. This will include the ease of understanding and use of the system. The third and final part of the questionnaire will have questions relating to the functionality of the prototype. These questions will capture the main objectives of this research and the main one being whether it gives correct answers within the shortest time possible. The questions will be structured in a way that calls for different answers including “Yes” and “No”. Appendix http://www.gradreports.com/colleges/colorado-technical-university-online References Gradreports.com (2016). Colorado Technical University - Online Reviews Retrieved 19August 2016, from http://www.gradreports.com/colleges/colorado-technical-university-online Coloradotech.edu (2016). History of CTU Retrieved 19August 2016, from http://www.coloradotech.edu/about/history
Purchase answer to see full attachment