ISEM 530 Systems Engineering Principles

1a: Object Oriented (O-O) is defined as the use of a methodology on the basis of various types of objects and the execution of the actions as per the manipulation and control of these objects.

b: Structured methods are the traditional approaches that are used in order to write down a particular code or program. Programmers in case structured methods break down the problem in various sub-sets to write a code for every individual problem. Object oriented method is a successor to the structured method to ease the software analysis and design. Structured methods lay more focus on the process whereas object oriented methods keep data as the primary focus. The former makes use of a top-down approach whereas latter uses bottom-up approach. Structured methods provide lesser flexibility; abstraction and more complexity which is resolved with the use of object oriented methods (Asagba, 2008).

2c: Key characteristics and attributes of O-O are as described below:

• Encapsulation: It is defined as the mechanism in which the data along with the various methods or functions are wrapped together in one single unit. It is also termed as data hiding in O-O as the contents of a particular class remain hidden from other classes.
• Inheritance: It is defined as the characteristic of O-O that allows acquiring of the properties of a particular class by another class. It allows the management of information in a hierarchical order (Snyder, 2014).
• Abstraction: It is the attribute of O-O that provides the users with the information on the functionality and hides the implementation details. The details regarding the activities performed by the object are provided to the users.
• Polymorphism: It is defined as the characteristic of O-O that allows a particular object with the ability to take up several different forms. For example, parent class object gets the ability to refer to an object of a child class.

d: Object Oriented was introduced in the early 1960s in MIT and a first programming language under this category was invented with the name as SIMULA. It was used for simulations and was created by Kristen Nygaard and Ole-Johan Dahl. Alan Kay at Xerox Parc further developed the idea and used Smalltalk as an object oriented programming language in the personal computer called Dynabook. Object Oriented Analysis and Design were not accepted as formal terms until 1982 when Grady Booch published a first paper on the same. 1980s was the period when Object Oriented Analysis and Design began to evolve and were being accepted by technocrats and researchers (Larman, 2005).

2: A System is defined as a collection of several components and objects that are linked together in some way or the other in order to achieve a particular goal. There are various characteristics that are associated with a system such as interaction, interdependence, integration and a central objective. Some of the essential elements of a system include input, output, environment, processing, interfaces and control (Tezu, 2013).

3: A System is an interdependent group of items that have a regular interaction with each other leading to the formation of a unified whole. Sub-System on the other hand is the derivative of a larger system. It is a set of elements that comprise of the components of a larger system and may act as an independent system.

4: System Analysis is defined as a process in which a particular system is studied by categorizing and classifying it into several different components to understand the level of interaction, purpose and details of the system and its components. There are several techniques that have been defined for the purpose of system analysis to identify the elements that are involved along with their utility and patterns (Subramanian, 2000).

5: System Design is defined as the understanding and interpretation of the system architecture, interfaces, modules and data in association with the system requirements. It is the process in which the application of system theory is carried out in order to proceed with the development of a certain product (Waldo, 2008). 

6: System Development Life Cycle (SDLC) is a framework that defined the several phases and tasks that are involved in the development of particular software or a system. SDLC is a process that described the stages such as planning, requirements analysis, designing, developing, testing & integration and deployment. There are several models that have been defined under SDLC which can be adopted for the development process such as Waterfall Model, Iterative Model, Spiral Model etc. 

7: There are primarily two approaches that can be used for the development of a system as Predictive SDLC and Adaptive SDLC.

Both of these approaches include the execution of tasks and activities to achieve an end product which is the developed system as per the requirements. There are stages that are involved in each of the two approaches with resources allocated with specific roles and responsibilities. However, both of these approaches have a lot many differences are well. The differences between predictive and adaptive SDLC are described below.

8: Spiral model is one of the adaptive SDLC models that follow the iterative approach for development. Identification is the first stage in this model which includes the gathering of the business requirements in the baseline spiral. The next stage is the design stage in which architecture, logical and physical models are created in the baseline spiral followed by the subsequent spirals. In the construction phase, Proof of Concept (POC) is created to get client feedback in the baseline spiral and the product is built in the subsequent spirals followed by risk analysis and evaluation from the customer.

9: Unified Process (UP) is defined as the use case driven and iterative approach for system development that is architecture-centric in nature. It is also referred as Unified Software Development Process that leverages Unified Modeling Language (UML) and also adheres to the system engineering meta-model. There are four phases that are associated with the development process under UP as inception, elaboration, conception and transition (Qi, 2015).

Unified Model Language (UML) is a general purpose modeling language and communication standard that is used in the field of software design and development. It comprises of notations and diagrams that are used to describe the boundary, structure and behavior of a particular system.

10 : The twelve principles as defined by Manifesto for Agile Development are as listed below:

• Delivery of the software shall be early and as per the schedule to seek higher customer satisfaction.
• The software shall have the ability to easily incorporate the changes without any delays.
• Working software shall be frequently delivered to the client.
• Business stakeholders shall be kept in close contact with the project team for better decision making.
• There shall be enhanced team collaboration, trust and motivation within the team.
• Face-to-face interactions shall be carried out for better communication.
• Progress shall be measured in terms of the delivery of the working software to the client.
• A consistent pace shall be followed in the development as well as delivery processes.
• Agility of the system shall be enhanced with the attention to the technical requirements along with the design.
• Simplicity shall be reflected in the project activities and end product.
• The project team shall be self-organized to achieve project goals.
• Feedbacks and regular reflections shall be carried out for achieving improvements (Agilemanifesto, 2017).

11:

13 : Work Breakdown Structure (WBS) is a project tool which is used to showcase a hierarchical representation of several work packages and sub-packages that are involved in a particular system. These packages in WBS are placed in different levels to provide an understanding on the project elements, activities, scope and structure. It is a tool which assists in the determination of project schedule and budget and also allows easier project management (Rcf, 2003).

14: Use cases are extremely significant in the system design and development process as they provide a lot of information associated with the system. Interaction and behavior of each of the system users is represented by the use cases along with their role in the system. A use case comprises of the system users in the form of the actors and the actions that are performed by them. It provides the system designers and developers with the ability to understand the level of interaction that is involved. 

15 a: A “requirement is” a listing and specification that is necessary to be included in the system or product that shall be developed.

b: “Functional Requirements” are the functionalities that shall be incorporated in the system that is being developed. These are the functional specifications in the form of business rules and capabilities associated with the system. These are the requirements that are measurable in nature.

c: “Non-Functional Requirements” are the system qualities that shall be incorporated in the system that is being developed. Some of the non-functional requirements of a system may include reliability, maintainability, scalability, performance, security and availability.

16: Project Management is a methodological approach that shall be followed in order to efficiently manage all of the project activities in order to achieve the project goals and objectives. Project Management includes initiation, planning, execution, control and closure of the project as the primary management activities. Each of these activities have sub-activities that are executed to ensure that the project meets the success criteria that is defined. 

17: Project Manager is the resource that is required to manage the entire project. The primary responsibilities of a Project Manager include the following:

• Allocation of duties and responsibilities to the project team
• Identification and management of the project risks
• Resolution of project disputes and conflicts through team meetings and discussions
• Communication with the project client along with project team
• Project planning including resource planning, schedule and budget planning
• Ensuring that the project deliverables are provided as per the schedule
• Motivating the project team members to achieve the project objectives and providing them with the guidelines to do so
• Status reporting to the project client and stakeholders 

18: There are several stakeholders that are involved in the projects. Some of the primary stakeholders include:

• Project Owner: Every project has a project client that has the highest interest in the project.
• Customers: A project is accomplished to provide the services or system to certain end users that are the customers in the project.
• Partners: There may be business partners that may have a direct connection with the project success or failure.
• Project Manager: The Project Manager is the most significant resource in the project that has a high degree of contribution along with the interest in the project.
• Project Team: Apart from the Manager, there are several resources that contribute towards the success of a project.
• Suppliers: There are third-parties that are associated with every project and suppliers form one of the significant stakeholders in the project. 

19: PMBOK is an acronym for Project Management Body of Knowledge. It is a project management methodology that provides the Project Manager with the guidelines to successfully manage and control a particular project. There are certain stages that are defined under PMBOK as project initiation, planning, execution, control and closure. Initiation stage includes the execution of feasibility analysis and project chartering. Risk management, communication strategy, schedule & budget design and allocation of responsibilities are carried out in the planning stage. Procurement, setting up of work environment, design and development are carried out in the execution phase followed by change management, testing and integration along with reviews and performance measurement in the control phase. The last phase under PMBOK is the closure phase in which acceptance and sign offs are achieved along with the system documentation and preparation of closure report (Chaves, 2016).

References

Agilemanifesto. (2017). Principles behind the Agile Manifesto. Agilemanifesto.org. Retrieved 25 July 2017, from http://agilemanifesto.org/principles.html

Asagba, P. (2008). A Comparative Analysis of Structured and Object-Oriented Programming Methods. Bioline.org.br. Retrieved 25 July 2017, from http://www.bioline.org.br/pdf?ja08064

Chaves, M. (2016). A new approach to managing Lessons Learned in PMBoK process groups: the Ballistic 2.0 Model. Retrieved 25 July 2017, from http://www.sciencesphere.org/ijispm/archive/ijispm-040102.pdf

Larman, C. (2005). History | Object-Oriented Analysis and Design | InformIT. Informit.com. Retrieved 25 July 2017, from http://www.informit.com/articles/article.aspx?p=360440&seqNum=8

Qi, X. (2015). The Software Process. Retrieved 25 July 2017, from http://digital.cs.usu.edu/~xqi/Teaching/CS2450F08/Notes/Ch3.SoftwareProcess.pdf

Rcf. (2003). Work Breakdown Structure. Retrieved 25 July 2017, from http://www4.rcf.bnl.gov/~videbaks/hft/cd1/DOE_guidance_wBS.pdf

Snyder, A. (2014). Encapsulation and Inheritance in Object-Oriented Programming Languages. Retrieved 25 July 2017, from http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.36.8552&rep=rep1&type=pdf

Subramanian, A. (2000). System Analysis. Retrieved 25 July 2017, from https://theses.lib.vt.edu/theses/available/etd-09012000-16240054/unrestricted/06Chapter4.pdf

Tezu. (2013). System. Retrieved 25 July 2017, from http://www.tezu.ernet.in/dba/new/faculty/heera/SAD.pdf

Waldo, J. (2008). On System Design. Retrieved 25 July 2017, from https://scholar.harvard.edu/files/waldo/files/ps-2006-6.pdf