System Development Methods And Techniques Assignment

Task 1: Time Management Plan

The time management plan is developed for managing the operations of the organization and development of integrated operations for the organization. The time management plan is being developed for scheduling the activities of the project so that it could be completed in the estimated time duration. The WBS or work breakdown structure is being developed for evaluating the concept of the project management concepts and principles for the time management principles and operations. A very minute detailed explanation of the activities of the project would be considered in forming the WBS for the project. The project constitutes a system development for allowing the employees of General Motors Holden to manage their car operations. The schedule for the project is being given below:

WBS	Task Name	Duration	Start Save Time On Research and Writing Hire a Pro to Write You a 100% Plagiarism-Free Paper. Get My Paper	Finish	Predecessors	Resource Names
0	Analysis and Designing of Information system for Holden	82 days	Thu 2/9/17	Fri 6/2/17
1	Project Initialization Phase	22 days	Thu 2/9/17	Fri 3/10/17
1.1	Organizational Analysis and Selection	7 days	Thu 2/9/17	Fri 2/17/17		Analyst
1.2	Requirement Analysis for the identified issues	5 days	Mon 2/20/17	Fri 2/24/17	2	Analyst
1.3	Identifying the key stakeholders	4 days	Mon 2/27/17	Thu 3/2/17	3	Analyst
1.4	Feasibility Analysis	2 days	Fri 3/3/17	Mon 3/6/17	4	Analyst
1.5	Analyzing the risk factors	4 days	Tue 3/7/17	Fri 3/10/17	5	Analyst
2	Project Implementation Phase	25 days	Mon 3/13/17	Fri 4/14/17
2.1	Analyzing the requirements for making plan	3 days	Mon 3/13/17	Wed 3/15/17	6	Analyst
2.2	Making plan for implementation	5 days	Thu 3/16/17	Wed 3/22/17	8	Analyst
2.3	Designing To Be process	6 days	Thu 3/23/17	Thu 3/30/17	9	Analyst
2.4	Comparing As Is with To Be process	6 days	Fri 3/31/17	Fri 4/7/17	10	Analyst
2.5	Developing the Logical and Physical topology	5 days	Mon 4/10/17	Fri 4/14/17	11	Analyst
3	Project Testing Phase	11 days	Mon 4/17/17	Mon 5/1/17
3.1	Developing testing program schedule	4 days	Mon 4/17/17	Thu 4/20/17	12	Analyst
3.2	Taking testing sample for analysis	7 days	Fri 4/21/17	Mon 5/1/17	14	Analyst
4	Project Training Phase	19 days	Tue 5/2/17	Fri 5/26/17
4.1	Making training manuals	5 days	Tue 5/2/17	Mon 5/8/17	15	Analyst
4.2	Developing training programs	4 days	Tue 5/9/17	Fri 5/12/17	17	Analyst
4.3	Providing training to the trainees	10 days	Mon 5/15/17	Fri 5/26/17	18	Analyst
5	Final Documentation and Closure	5 days	Mon 5/29/17	Fri 6/2/17
5.1	Developing final report for the project	3 days	Mon 5/29/17	Wed 5/31/17	19	Analyst
5.2	Signing off the documents	1 day	Thu 6/1/17	Thu 6/1/17	21	Analyst
5.3	Project is closed	1 day	Fri 6/2/17	Fri 6/2/17	22	Analyst

Table 1: Project Schedule for the Analysis and Designing of Information system for Holden

(Source: Created by the Author)

The schedule had been able to identify that the project would start on 9^th February, 2017 and it would take 82 days and it would complete on 2^nd June, 2017.

Figure 1: “TO BE” diagram for Holden car purchase process

(Source: Created by Author)

The developed process of “AS IS” in the previous assignment with respect to the information system for Holden Car Company, it is identified that there is no involvement of call center of support staffs so that the customers can pre-book their visit to the car showroom. Therefore, the “TO BE” diagram for the processing of car purchase by customers using the information system. The “AS IS” process does not have any option for customers to confirm that a car is available in the showroom or not.

Physical Network topology

Figure 2: Entity Relationship diagram for Holden car purchase system

(Source: Created by Author)

Customer

Attribute	Data Type
Customer ID (PK)	int (20)
Customer Name	Varchar (20)
Customer Address	Varchar (20)
Customer Contact	int (20)

Attribute	Data Type
CallCenter ID (PK)	int (20)
CallCenter Contact	int (20)
CallCenter staff	Varchar (20)

Attribute	Data Type
SupportStaff ID (PK)	int (20)
SupportStaff Name	int (20)
SupportStaff Address	Varchar (20)
SupportStaff Contact	Varchar (20)

Attribute	Data Type
Mod ID (PK)	int (20)
Mod Name	Varchar (20)
Description	Varchar (20)

The testing phase of the project consists of evaluation of the system developed for General Motor Holden. The various types of testing for the system developed in project are,

Acceptance Testing: The acceptance testing is developed for the analysis of the system operations and integration of the operations (Dennis, Wixom and Tegarden 2015). The acceptance testing evaluates the operations of the system developed for Holden and its projected outcome from the implementation. The acceptance testing evaluates the functional output from the system developed.

Alpha Testing: The testing of the system would be done by Alpha testing and it would involve the potential users of the system for getting the output. An unbiased team would use the device for some testing period (Khalili and Duecker 2013). The alpha testing would form the assurance of the functions of the system in a controlled environment.

Backward Compatibility Testing: The backward compatibility testing is being done for evaluating the concept of the functions of the devices and its function with respect to the functions of the Holden. The system developed would be evaluated for the analysis of the developed operations with the system developed for Holden.

The training consists of four steps that would be followed for providing training to the users of the system such as Administrators, SR, Investors, and Customer Representatives. The steps of training involves,

Task 2: “TO BE” Process

Development of Training Manuals: The first step of the training process is the development of the training manuals as it would provide support to the trainees for understanding the system. The manuals would serve as a training guide for assisting the trainees for the study process (Lewis 2016).

Schedule of Training Programs: The training programs would be developed and scheduled so that the users can get the benefit of the learning experience for the system development and operational activities.

Provide Training to Users: The users of the system would receive the training from the trainers and it would help them to develop the understanding for the system working principles and functions (Montgomery 2017).

Evaluation of Trainees: The evaluation is being done for reviewing whether the trainees have understood the training provided to them.

In basic words coordinate cutover approach is an immediate approach where old framework is cut and over compose by new framework. The direct cutover approach makes the changeover from the old framework the new framework to happen instantly when the new framework winds up plainly operational (Tsui, Karam and Bernal 2016).

This is a slightest costly strategy among every one of the four however includes high danger of information misfortune. With the direct cutover technique, organization can’t return to the old framework as a reinforcement choice. Coordinate cutover includes more dangers of aggregate framework disappointment and if there is a framework disappointment in wellbeing focus then it will be hard to store data of youngster who visits wellbeing focus and this will bring about shameful stockpiling of information (Fuggetta and Di Nitto 2014). In any case, as there is absence of assets, this approach will be a conceivable alternative in light of its ease application among every one of the four methodologies.

Objective

 The primary objective of the project is for identification of the factors such as management plans, system, time, hierarchical structure of operations, and working habitat of people that play a major role in the development of the organization. The case study for the project is of General Motors Holden and it would evaluate the key factors of the management system in the company. The development of the information system and its role would form the basic evaluation of the inbuilt system development for the organization. The General Motor Holden would implement the system integration for their processes and it would develop their operational activities.

Process Undertaken 

The project is developed for evaluating the concept of the management activities and development of the operations in the organization of the operations. The development of the project operations would form the evaluation of the processes taken for the development of the activities of the Holden. The cost reduction, improvement strategies, filtering of the activities, and development of plan would be evaluated in the project processes. The development of the system indulged operations would form the integrated development models in the organization. The avoidance of the system integration issues would be developed for the evaluation of the system integration for the operations of the organization.

Scope 

The project would be developed for the integration of the activities and implementation of the operations. The development of project scope would integrate the development of the individual’s roles and responsibilities for the evaluation of the integrated operations for the organization. The team members would have to form the integrated system development and operational integration. The overall development would lead to the achievement of project goals and responsibilities.

The development of the operations would be implemented for forming the integration of the operations and development of the functions. The development of operations would be formed for the integrations of the development models for the organization. The facilities of the organization would allow the influence on the customers and provide good services to them. The development of the project would integrate the implementation of the system development for the project operations.

References

Buede, D.M. and Miller, W.D., 2016. The engineering design of systems: models and methods. John Wiley & Sons.

Chitchyan, R., Rashid, A., Sawyer, P., Garcia, A., Alarcon, M.P., Bakker, J., Tekinerdogan, B., Clarke, S. and Jackson, A., 2015. Survey of aspect-oriented analysis and design approaches.

David, O., Ascough, J.C., Lloyd, W., Green, T.R., Rojas, K.W., Leavesley, G.H. and Ahuja, L.R., 2013. A software engineering perspective on environmental modeling framework design: The Object Modeling System. Environmental Modelling & Software, 39, pp.201-213.

De Lemos, R., Giese, H., Müller, H.A., Shaw, M., Andersson, J., Litoiu, M., Schmerl, B., Tamura, G., Villegas, N.M., Vogel, T. and Weyns, D., 2013. Software engineering for self-adaptive systems: A second research roadmap. In Software Engineering for Self-Adaptive Systems II (pp. 1-32). Springer Berlin Heidelberg.

Dennis, A., Wixom, B.H. and Tegarden, D., 2015. Systems analysis and design: An object-oriented approach with UML. John Wiley & Sons.

Fenton, N. and Bieman, J., 2014. Software metrics: a rigorous and practical approach. CRC Press.

Fuggetta, A. and Di Nitto, E., 2014, May. Software process. In Proceedings of the on Future of Software Engineering (pp. 1-12). ACM.

Hassan, M.M., Afzal, W., Lindström, B., Shah, S.M.A., Andler, S.F. and Blom, M., 2016, April. Testability and software performance: a systematic mapping study. In Proceedings of the 31st Annual ACM Symposium on Applied Computing (pp. 1566-1569). ACM.

Jorgensen, P.C., 2016. Software testing: a craftsman’s approach. CRC press.

Khalili, N.R. and Duecker, S., 2013. Application of multi-criteria decision analysis in design of sustainable environmental management system framework. Journal of Cleaner Production, 47, pp.188-198.

Lewis, W.E., 2016. Software testing and continuous quality improvement. CRC press.

Montgomery, D.C., 2017. Design and analysis of experiments. John Wiley & Sons.

Tsui, F., Karam, O. and Bernal, B., 2016. Essentials of software engineering. Jones & Bartlett Learning.

Valacich, J.S., George, J.F. and Hoffer, J.A., 2015. Essentials of systems analysis and design. Pearson Education.

Vyatkin, V., 2013. Software engineering in industrial automation: State-of-the-art review. IEEE Transactions on Industrial Informatics, 9(3), pp.1234-1249.

Wasson, C.S., 2015. System Engineering Analysis, Design, and Development: Concepts, Principles, and Practices. John Wiley & Sons.