Q.1 Explain System Engineering Hierarchy?

Ans:

Fig: software engineering hierarchy

System engineering encompasses a collection of top-down and bottom-up methods to navigate the hierarchy
illustrated in Figure. The system engineering process usually begins with a “world view.” That is, the entire
business or product domain is examined to ensure that the proper business or technology context can be
established. The world view is refined to focus more fully on specific domain of interest. Within a specific
domain, the need for targeted system elements (e.g., data, software, hardware, people) is analyzed. Finally, the
analysis, design, and construction of a targeted system element is initiated. At the top of the hierarchy, a very
broad context is established and, at the bottom, detailed technical activities, performed by the relevant
engineering discipline (e.g., hardware or software engineering), are conducted.
It is important to note that the system engineer narrows the focus of work as he
or she moves downward in the hierarchy just described. However, the world view portrays a clear definition of
overall functionality that will enable the engineer to understand the domain, and ultimately the system or product,
in the proper context.

OFFICE ADDRESS: PLOT NO.381, PANCHSHEEL LIBRARY, III RD FLOOR, GANDHI NAGAR, NAGPUR 440033
CONTACT NO. : 9422213859, 9766914284
Q.2 Explain the concept of system modeling?
Ans: System engineering is a modeling process. Whether the focus is on the world view or the detailed view, the
engineer creates models that

• Define the processes that serve the needs of the view under consideration.
• Represent the behavior of the processes and the assumptions on which the behavior is based.
• Explicitly define both exogenous and endogenous input to the model.
• Represent all linkages (including output) that will enable the engineer to better understand the view.

To construct a system model, the engineer should consider a number of restraining factors:
1. Assumptions that reduce the number of possible permutations and variations, thus enabling a model to
reflect the problem in a reasonable manner.
2. Simplifications that enable the model to be created in a timely manner.
3. Limitations that help to bound the system.
4. Constraints that will guide the manner in which the model is created and the approach taken when the
model is implemented.
5. Preferences that indicate the preferred architecture for all data, functions, and technology.

Q.3 Explain business process engineering?

Ans:

OFFICE ADDRESS: PLOT NO.381, PANCHSHEEL LIBRARY, III RD FLOOR, GANDHI NAGAR, NAGPUR 440033
CONTACT NO. : 9422213859, 9766914284
The goal of business process engineering (BPE) is to define architectures that will enable a business to use
information effectively. The BPE hierarchy includes:
1. Information strategy planning (ISP): the world view is achieved through information strategy planning
(ISP). ISP views the entire business as an entity and isolates the domains of the business (e.g., engineering,
manufacturing, marketing, finance, sales) that are important to the overall enterprise. ISP defines the data
objects that are visible at the enterprise level, their relationships, and how they flow between the business
domains.
2. Business area analysis (BAA): The domain view is addressed with a BPE activity called business area
analysis (BAA). As the system engineer begins BAA, the focus narrows to a specific business domain. BAA
views the business area as an entity and isolates the business functions and procedures that enable the
business area to meet its objectives and goals.
3. Business system design (BSD): In BSD the basic requirements of a specific information system are modeled
and these requirements are translated into data architecture, applications architecture, and technology
infrastructure.
4. Construction and integration: construction and integration focuses on implementation detail. The
architecture and infrastructure are implemented by constructing an appropriate database and internal data
structures, by building applications using software components, and by selecting appropriate elements of a
technology infrastructure to support the design created during BSD. The integration activity also places the
new information system into the business area context, performing all user training and logistics support to
achieve a smooth transition

Q.3 Explain product engineering?

Ans:

OFFICE ADDRESS: PLOT NO.381, PANCHSHEEL LIBRARY, III RD FLOOR, GANDHI NAGAR, NAGPUR 440033
CONTACT NO. : 9422213859, 9766914284
The goal of product engineering is to translate the customer’s desire for a set of defined capabilities into a
working product. To achieve this goal, product engineering—like business process engineering—must derive
architecture and infrastructure. The architecture encompasses four distinct system components: software,
hardware, data (and databases), and people. The Product engineering hierarchy includes:

1. requirements engineering: the world view is achieved through requirements engineering. The overall
requirements of the product are elicited from the customer. These requirements encompass information
and control needs, product function and behavior, overall product performance, design and interfacing
constraints, and other special needs.
2. component engineering: System component engineering is actually a set of concurrent activities that
address each of the system components separately: software engineering, hardware engineering, human
engineering, and database engineering.
3. software engineering: For software engineering, this means analysis and design modeling activities and
construction and integration activities that encompass code generation, testing, and support steps. The
analysis step models allocated requirements into representations of data, function, and behavior. Design
maps the analysis model into data, architectural, interface, and software component-level designs.

Q.4 Discuss in detail the various steps of requirements engineering?

Ans: Requirements engineering provides the appropriate mechanism for understanding what the customer wants,
analyzing need, assessing feasibility, negotiating a reasonable solution, specifying the solution unambiguously,
validating the specification, and managing the requirements as they are transformed into an operational system.
The requirements engineering process can be described in five distinct steps:

• requirements elicitation
• requirements analysis and negotiation
• requirements specification
• requirements validation
• requirements management

Requirement elicitation is the action of discovering system requirements through consultation with stakeholders.
Some of the sources of this discovery could be system documents, domain knowledge, and market studies.
Requirement analysis and negotiation is possessing the ability to analyze requirements in details and negotiate
them with stakeholders on which requirements are to be considered.
Requirement specification or documentation is the action of documenting agreed requirements at a certain level
of detail.
Requirement validation is the process of reviewing requirements for clarity, consistency and completeness.
Requirements management is a set of activities that help the project team to identify, control, and track
requirements and changes to requirements at any time as the project proceeds.

OFFICE ADDRESS: PLOT NO.381, PANCHSHEEL LIBRARY, III RD FLOOR, GANDHI NAGAR, NAGPUR 440033
CONTACT NO. : 9422213859, 9766914284