1. INCOS describes systems engineering as integrating all the disciplines and specialty groups into a team effort forming a structured development process that proceeds from concept to production to operation. Further that systems engineering considers both the business and the technical needs of all customers with the goal of providing a quality product that meets the user needs. (INCOSE 2012)? Please explain what the INCOS definition means by using an example of a project in a large organisation you have studied.
2. Please explain with an example the term “Systems of Systems“?
3. Please explain the following diagram?
4. Please explain how applications systems like SAP influence knowledge management and particularly decision making in a project, program and portfolio environment?
5. Please provide examples of how applications systems might hinder performance monitoring or managing change?
6. SEBoK talks about Generic Life Cycle Models. Please explain with examples Generic Life Cycle Models?
7. Is it possible for scenario analysis to be performed so that it would be useful to an organisation like BP? What would be required to ensure that any models are an accurate reflection of the real world?
8. What is Enterprise Project Portfolio Management (EPPM) and what does Oracle say are the advantages of EPPM?
9. What systems thinking is and what it is trying to achieve?
10. Please explain the following diagram?
Applications Systems and their Impact on Knowledge Management and Decision-Making in the Project Environment
1. As per INCOS, the system engineering is a set of rules that would be formed for ensuring that the deployment of the effective alignment model. Considering the example of Woolworths Online Retail Store, the system engineering for the online payment processing development would be helpful for forming the utilization of the successive payment system development. The set of privacy rules are helpful for integrating the team effort and forming the utilization of the information system development of the structured team effort that constitute the concept of payment platform development to the operations of the customer payment processing. The payment platform system engineering extends to the consideration of the both technological and business needs for the customers with the goal of enabling performance improvement and meeting the easy payment needs of the customers of Woolworths. The complete process of developing the smart development methods can be easily developed for listing the utilization of the effective and improved communication methods with the help of system engineering principles so that the customers of Woolworths would get the benefit of increased customer satisfaction.
2. Systems of systems is referred to the concept of the forming a collection of some specific system that are either dedicated or task oriented in nature. The system is practically developed for any specific types of the work or operation and it combines the system capabilities with the resources for developing more effective and improved system. The systems of systems are complex in nature and it comprise of the capability of providing more functions than the sum of functions provided by the unit systems forming the systems of systems. The development is possible because the individual system have independent work capabilities. However, when two or more system combines, their interaction typically helps in forming the improvement of the activities supporting the deployment of the newer abilities. For example- the space exploration systems are collectible of simple systems that have individual capabilities. However, the simple systems are combined for achieving the space system analysis and much greater functions. The radio communication system would be developed to form the communication from the space to the station in Earth.
3. The above diagram represents the individual concepts of the three subjects namely systems engineering, system implementation, and project/system management. The Venn diagram has been used for understanding the relation between the three study subjects. The system engineering, system implementation and project/system management are different studies. However, some of their principles and tools are related to each other. The diagram would provide us the following explanations,
Hindrance to Performance Monitoring and Change Management
Explanation 1: The system engineering, system implementation, and project/system management have Lifecycle Planning and estimation, change analysis and management, and QA, V&V, continuous process improvement as the common discipline for all of them.
Explanation 2: The system engineering and system implementation have production planning and analysis, system integration, Lifecycle Planning and estimation, change analysis and management, and QA, V&V, continuous process improvement as the common discipline between them.
Explanation 3: The system engineering and project/system management have business case analysis, system engineering management, Lifecycle Planning and estimation, change analysis and management, and QA, V&V, continuous process improvement as the common discipline between the two.
Explanation 4: The system engineering and project/system management have supply chain management, system implementation management, Lifecycle Planning and estimation, change analysis and management, and QA, V&V, continuous process improvement as the common discipline between the two.
Explanation 5: Rest of the functions of systems engineering, system implementation, and project/system management respectively are exclusive (not similar or related) among them.
4. SAP provides an extensive platform for the ERP processes for all scales of business organization. It helps in data management, business intelligence, and customer relationship management. The project, program and portfolio environment is dependent on the deployment of the effective and improved functional development for the organization. The use of the practically developed SAP would help in the following functions,
SAP would help in developing exclusive information system that would be capable for the deployment of the effective data management for project, program and portfolio environment. It would help in supporting the major activities of project, program and portfolio environment by providing some information on it from the previous documentation and reports.
It would provide opportunities for integrating the business intelligence in the project, program and portfolio environment so that the system thinking capabilities can be improved and the development of the activities supporting the development of the smart decision making.
SAP helps in building of client information processing so that the project, program and portfolio environment can be effectively developed by considering the requirements of the clients in the first place.
6. According to SEBoK, the Generic Life Cycle Models is the representation of the most common life cyles model for the system development as most of the system development projects would have difference in executio of the project/system development. It is clear from the study that one-fits-all project lifecycle does not exist in real life. Hence, it is possible that the system development lifecycle can be normalised in form of the Generic Life Cycle Models so that the complete system development can be executed by the help of it. The model comprises of concept definition, system definition, realization, production, support, utilization, and retirement stages. Each of the stage is followed by a decision process, in which the key stakeholders would be required to choose whether to proceed to next stage, re-evaluate the current phase, or work in the current state.
BKCASE Editorial Board. 2017. The Guide to the Systems Engineering Body of Knowledge (SEBoK), v. 1.9. R.D. Adcock (EIC). Hoboken, NJ: The Trustees of the Stevens Institute of Technology. Accessed 31 May 2018. www.sebokwiki.org.
PMI. 2013. Program Management Standard. Penn, USA. Project Management Institute.
Rainey, L. B., & Tolk, A. (Eds.). (2015). Modeling and simulation support for system of systems engineering applications. John Wiley & Sons.
Sykes, T. A. (2015). SUPPORT STRUCTURES AND THEIR IMPACTS ON EMPLOYEE OUTCOMES: ALongitudinal FIELD STUDY OF AN ENTERPRISE SYSTEM IMPLEMENTATION. Issues, 11401.
Mailloux, L. O., Garrison, C., Dove, R., & Biondo, R. C. (2015, October). Guidance for Working Group Maintenance of the Systems Engineering Body of Knowledge (SEBoK) with Systems Security Engineering Example. In INCOSE International Symposium (Vol. 25, No. 1, pp. 1004-1019).
INCOSE. 2012. INCOSE Systems Engineering Handbook, version 3.2.2. San Diego, CA, USA: International Council on Systems Engineering (INCOSE), INCOSE-TP-2003-002-03.2.2.
Walden, D. D., Roedler, G. J., & Forsberg, K. (2015, October). INCOSE Systems Engineering Handbook Version 4: Updating the Reference for Practitioners. In INCOSE International Symposium (Vol. 25, No. 1, pp. 678-686).