IGNOU BCS-051 Software Engineering December 2022 - Exam Solutions.docx

BACHELOR OF COMPUTER APPLICATIONS
(BCA) (Revised)
Term-End Examination
December, 2022
BCS-051 : INTRODUCTION TO SOFTWARE
ENGINEERING
1. (a) Develop SRS for Online Examination Form Submission System (OEFSS). SRS should be in IEEE
format. Make necessary assumptions. [ Dec. 2022]
Answer :
1. Purpose :
1:This Web Application Provides facility to submit Online Examination Form and Generate the
Academic Results as well as display news related to Exams.
2: It saves Time as it allows number of Departmental students to login and fill the exam form
at a time and submit it.
3: After submitting the exam form, Exam Fees challan will be automatically generated,
Student can take print out of that Challan.
4: Administrator has a privilege to Create, Generate, modify, delete, Exam Form, Hall Ticket,
Result, any Exam related news or any Content on this Web Application.
5: Teacher or supervisor can Generate a patterns (Block Creation) of a Sitting Arrangement
as well as Report ([Roll Number][ Exam Seat Number],name, [Internal Exam Marks],
Signature) and take a printout of it.
2. System Scope
This system will be used by the students, teachers and administrator of an autonomous institute
to keep details of the students related to their exams and generating reports as well as results.
3. Requirements
This section gives the list of Functional and non-functional requirements which are applicable to the
Online Exam Form Submission and Academic Result Generation System.
3.1. Functional Requirements
Functional requirements are nothing but the services provided by the system to its end users.
3.1.1. User types:
There are three kinds of user types in this Application.
Student module.
Teacher / Supervisor module.
Administrator module.

The functionality of each module is as follows. :

Student module:
The student will logon to this web Application and can fill examination form, Can take
printout of Bank Challan after generating it.
Examination form will be automatically generated following things: Roll Number, Name of
Student, Examination Name or Semester, Subject Code, Subject Name, Number of Backlogs
(if any), Exam fees, etc.
Student will have facility to select the subject, where he will appear in exam.

Administrator module:
The administrator can create, modify, insert, update , delete any stuff on this web
application. He should be approve Exam from to generate a Exam hall tickets for students. He
can manage other Accounts related to this web application (add user, delete user..etc.).
He can upload any exam related document on this web application.
Exam Hall Ticket will Contains information like:
Student information (Name, Roll No/Exam Seat Number, Mothers Name, PRN, Exam Center
Code, etc.).
Subject Code, Subject Name, Exam Date, etc.

Teacher module:
Teacher will logon to this web Application and can generate report for
that exam and also generate Exam sitting arrangement (Block creation) and take a printout.
In block creation teacher can generate some exam sitting
arrangement patterns by just giving total number of students appearing for exam,
Total number of rooms will use to conduct exam, total number of benches in room,
examination name and date of examination.
Teacher will enter marks (Internal + External).
Depending upon Internal or External or both marks, System will generate Report as well as
ledger and Result if student cleared all subjects then result will contain percentage, overall
grade.
In report generation following things will auto generate: Name of the Exam, Date, [Exam seat
No.] or [Roll No.], name of student, [internal examination marks], Signature, etc.
Blank space for total number of student, Total number of student present, Total number of
student absent, name of the supervisor, signature of supervisor etc.
3.1.2 Interface Requirements
This section describes how the software interfaces with
other software products or users for input or output.
3.1.3 User Interface

Application will be accessed through a Browser Interface. The interface
would be viewed best using 1024 x 768 and 800 x 600 pixels resolution setting. The software
would be fully compatible with Microsoft Internet Explorer and Mozilla Firefox for version 7
and above. No user would be able to access any part of the application without logging in to
the system.
3.2 Non Functional Requirements
3.2.1. User Interfaces
Application will be accessed through a Browser Interface. The
inter face would be viewed best using 1024 x 768 and 800 x 600 pixels resolution setting.
The software would be fully compatible with Microsoft Internet Explorer and or Mozilla Firefox
for version 7 and above. No user would be able to access any part of the application without
logging in to the system.
3.2.2 Hardware Interfaces
Server Side:
> Operating System: Windows XP or Above Versions or any Linux Distros
> Processor: Pentium 4.0 GHz or higher
> RAM: 512 Mb or more
> Hard Drive: 10 GB or more
Client side:
 Operating System: Windows XP or above, MAC OS or any UNIX Distros.
 Processor: Pentium IV or 2.0 GHz or higher.
 RAM: 256 Mb or more
3.2.3 Software Interfaces
Client Side :
. Web Browser, Windows XP or Above Versions / any Unix Distro/ MAC OS
Web Server:
. Web Browser, Windows XP or Above Versions / any Unix Distro/ MAC OS
3.2.4 Communications Interfaces
The Customer must connect to the Internet to access the Website:
 Dialup Modem of 52 kbps or more.
 Broadband Internet
 Dialup or Broadband Connection with an Internet Provider.
4. Other Non-functional Requirements
4.1. Performance Requirements
Some Performance requirements identified is listed below:
 The database shall be able to accommodate a minimum of 5,000 records of students.
 The software shall support use of multiple users at a time. There are no other specific
performance requirements that will affect development.
4.2. Safety Requirements

The database may get crashed at any certain time due to virus or operating system failure.
Therefore, it is required to take the database backup.
4.3. Security Requirements
Some of the factors that are identified to protect the software from accidental or malicious
access, use, modification, destruction, or disclosure are described below.
1. Keep specific log or history data sets.
2. Assign certain functions to different modules
3. Restrict communications between some areas of the program
4. Communication needs to be restricted when the application is validating the user or license.
(i.e., using https).
4.4. Software Quality Attributes
The Quality of the System is maintained in such a way so that it can be very user
friendly to all the users.
The software quality attributes are assumed as under:
1) Accurate and hence reliable. 2) Secured. 3) Fast speed. 4) Compatibility.
(b) Explain Prototype Model, with the help of an example. What are its advantages and
disadvantages over Waterfall Model ? [Dec. 2022]
Answer :
Prototyping Model
In this model, a working model of actual software is developed initially. The prototype is just like
sample software having lesser functional capabilities and low reliability and it does not undergo
through the rigorous testing phase. Developing a working prototype in the first phase overcomes
the disadvantage of the waterfall model where the repotting about serious errors is possible only
after completion of software development.
The working prototype is given to the customer for operation. The customer, after its use, gives the
feedback. Analysing the feedback-given-by the customer, the developer refines, adds the
requirements and prepares the final specification document. Once the prototype becomes
operational, the actual product is developed using the normal waterfall model. Below depicts the
prototyping model:
.The prototype model has the following features:
1. It helps in determining user requirements more deeply.
2. At the time of actual product development, the customer feedback is available.
3. It does consider any types of risks at the initial level.

Advantages of prototype model
There are various advantages of prototype model. Some of them are discussed below:
1. Active involvement : With this approach, consumers are actively participating in the
development process, making it simpler to tailor the model to their preferences.
2. Easy detection of missing functionality: The prototype model’s lacking functionality is
clearly discernible. The chances of failure are decreased as a result. Additionally, confusing
or challenging functions might be found.
3. Quick feedback : Feedback from customers is provided much more quickly since they may
engage directly with the prototype model. Customers may rapidly offer their opinions and
indicate adjustments that are necessary for the project, and the developers can
subsequently adjust the project as required.
4. Customer satisfaction : The prototype model offers much higher levels of client satisfaction.
Early on, the consumer has the opportunity to touch and feel the product, which helps them
better comprehend its requirements to create the operational version of their idea that adds
satisfaction.
5. Flexibility :The prototype model’s design is adaptable. It is easily transferable to the
interests and requirements of the client or the developer
6. Saves money : A prototype model might make it easier to see mistakes during the project’s
early phases. As a result, the project’s total cost and duration are decreased. The use of
prototype models enables the developer to anticipate areas of expense that weren’t
previously considered.
Disadvantages of prototype model
1. Time-consuming : The creation of the prototype model takes a lot of time. Multiple
prototypes are tested before the final product is developed, which takes a lot of time.
2. Misconception regarding the arrival of the final product :Early on, the consumer has the
opportunity to interact directly with the prototype. Because of this, the buyer could believe
that the real goods would likewise come earlier than expected, which could result in
confusion.
3. Poor decision-making : The creator is constantly concerned with the quality of their
creation. However, they could make bad choices about the prototype’s quality while rushing
to create it, which could have an impact on the final product.
4. Misunderstanding regarding the final version : Customers may become annoyed and upset
with the prototype model and lose interest in the final product. Customers may believe that
the final version will have the same flaws even though it is enhanced and polished.
5. High upfront cost : Using a prototype model throughout the last phases of development can
help you save money. However, there are up-front expenditures associated with creating a
prototype model. Additionally, since there’s a potential that the entire prototype would be
discarded, the money spent on producing it can be utterly wasted.
6. Insufficient analysis :There is a potential that the developer may focus on a particular
prototype and neglect to do a thorough evaluation of the entire project. As a consequence,
the developer may miss better options, forget about important details, and the project as a
whole could be poorly designed, necessitating difficult maintenance

(c) What is a Structure Chart ? Explain with the help of an example. [Dec 2022]
Answer :
A structure chart (SC) decomposes the high level system into multiple, executable tasks. It follows
the top-down design approach and represents module hierarchy in tree structure. Structure chart
essentially describes the list of functions, sub-functions along with their relationship that constitute
a system along with data and control flow. Structure chart is the next step after DFD during design
and implementation as SC provides more details than DFD. SC uses information from Data dictionary
which is detailed in subsequent sections. .
A structure serves following purposes during design:
• Breaks the system into smaller and executable functional tasks
• Depicts the complexity and size of the system
Element of Structure Chart
The main building blocks of Structure Chart are given below along with their symbols
• Module depicts a function or a sub-function and is represented by a rectangle. If a function
invokes multiple sub-functions, then the main module branches to .sub-modules. It is basically a unit
of execution which accepts input parameters and produces output parameters.
It is denoted as follows:
Main module invoking sub modules is depicted below:
• Condition decides which module is to be invoked based on the condition. It is denoted by a
diamond. A conditional invocation of sub module is denoted by in the main module.
• Loop indicates the repetition of one or more modules and is depicted by a curved arrow
Execution of sub modules within a loop is denoted as follows:
• Data couple is shown by an arrow with empty circle and it denotes the data that is-flown from
one module to another. The flow of information has a direction.

• Control Flow is shown by an arrow with filled circle and denotes the function call from one
module to another.
Data and control flow are depicted below:
• Devices such as peripheral devices and external interfaces are denoted by·
• Software infrastructure and connections to external systems, databases, ERP
systems are denoted by
Process for Construction of a Structure Chart
Let us construct a structure chart for calculating a hotel bill for a customer. This high level function is
decomposed into four sub functions:
 Calculate total order amount
 Calculate value added tax (VAT) ,
 Calculate service charge
 Calculate any discounts applicable for the customer
Each of these sub-functions take input and output parameters. The structure chart along
with data flow is shown in Figure

2. (a) Draw the zero and first level DFDs for Online Examination Form Submission System (OEFSS)
Make necessary assumptions. [Dec. 2022]
Answer :
Zero Level DFD
Level – 1 DFD
Student Teacher
Administrator
0
Online
Examination
Form
Submission
Registers for exam
Receive Exam Hall ticket Assign Marks
Student details
Manage Exam Registration /Hall Ticket
1.0
Student Module
2.0
Teacher Module
3.0
Administrator
Module
Student
Student Database
Exam Registration Database
Course Database
Marks Database
Course Database
Exam Registration Database
Student Database
Hall Ticket Database
Hall Ticket Database
Teacher
Administrator
Login / Password
Exam registration Receipt
/ Hall Ticket
Login / Password
Exam Seating arrangement
/ Assign Marks
Login / Password
Manage Registration details
/ Generate Hall Tickets

(b) Draw GANTT Chart for the development of Online Examination Form Submission System (OEFSS).
[Ded. 2022]
The following table shows the tasks, dependencies, and estimated times a
project manager might input to a basic GANTT chart for a software development
project for Online Student Admission system
Project start date: 12 June 2023
Task
Identifier
Task Description Predecessor
Task(s)
Time (Weeks)
1 Establish project - 2
2 Establish customer
requirements
1 3
3 Produce software
specification documents
2 4
4 Write test plans 3 1
5 Write code 3 2
6 Developer testing 5 1
7 System testing 4, 6 3
8 Write customer
documentation
3 3
Task 1 has no predecessors, and can thus start on 12 June. The GANTT chart
shows the task as a box starting on 12 June and finishing on 25th
June on the
horizontal access. Task 2 requires Task 1 to be completed, and the duration is
three days, so the box covers the Week 3 to 5 till 16th
July. The line from the
finish of Task 1 to the start of Task 2 indicates the dependency. Note that Tasks 4,
5 and 8 all require Task 3 to be completed, and have no other dependencies, so
these all start on the same date. The chart below show all seven days of the week,
but often, weekend days are excluded.
ID Activity Duration
(Weeks)
Timeline
Week-
1
12/06-
18/06
Week-
2
19/06-
25/06
Week-
3
26/06-
02/07
Week-
4
03/07-
09/07
Week-
5
10/07-
16/07
Week-
6
17/07-
23/07
Week-
7
24/07-
30/07
Week-
8
31/07-
06/08
Week-
9
07/08-
13/08
Week-
10
14/08-
20/08
Week-
11
21/08-
27/08
Week-
12
28/08-
03/09
Week-13
28/08-
03/09
Week-
14
04/09-
10/09
Week-
15
11/09
17/09
1 Establish
project
2 `
2 Establish
customer
requirements
3
3 Produce
software
specification
documents
4
4 Write test plans 1
5 Write code 2
6 Developer
testing
2
7 System testing 3
8 Write customer
documentation
3

3. (a) Draw ERD for Online Examination Form Submission System (OEFSS).. Make necessary
assumptions.
1
N
N
N
N
Student
Student_Id
Student_Name
Course_id
Exam_Id
Registers
Examination
Online Exam Form
Submission
System
Login_Id Password
attend
Exam_Id
Administrator
Admin_Id Admin_Role
Admin_rights
Exam_Name
Subject_Id
Conducts
has
Subject
Subject_Name
generate
s
Hall Tickets
Exam_Roll_No
Exam_id
Student_id
Student_Name
Exam_Center_No
Exam_Center_Address
Manage
Subject_Name
Date
Time

(b) Briefly explain different levels of SEI-CMM [Dec. 2022]
Answer : Levels Of SEI-CMM
The process models are based on various software development phases whereas the capability
models have an entirely different basis of development. They are based upon the capabilities of
software. It was developed by Software Engineering Institute (SEI). In this model, significant
emphasis is given to the techniques to improve the "software quality" and "process maturity". In this
model a strategy for improving Software process is devised. It is not concerned which life cycle mode
is followed for development. SEI has laid guidelines regarding the capabilities an organisation should
have to reach different levels of process maturity. This approach evaluates the global effectiveness
of a software company.
It defines five maturity levels as described below. Different organisations are certified for
different levels based on the processes they follow.
1. Level-1 (Initial): At this maturity level, software is developed an ad hoc basis and no
strategic approach is used for its development. 'The success of developed software entirely
depend upon the skills of the team members. As no sound engineering approach is followed,
the time and cost of the project are not critical issues. In Maturity Level 1 organisations, the
software process is unpredictable, because if the developing team changes, the process will
change. The testing of software is also very simple and accurate predictions regarding
software quality are not possible. SEI's assessment indicates that the vast majority of
software organisations are Level 1 organisations
2. Level 2 (Repeatable): The organisation satisfies all the requirements of Level 1. At this
level, basic project management policies and related procedures are established. The
institutions achieving this maturity level learn with experience of earlier projects and
reutilise the successful practices in on- going projects. The effective process can be
characterised as practised, documented, implemented and trained. In this maturity level,
the manager provides quick solutions to the problem encountered in software
development and corrective action is immediately taken. Hence, the process of
development is much disciplined in this maturity level. Thus, without measurement,
sufficiently realistic estimates regarding cost, schedules and functionality are
performed. The organisations of this maturity level have installed basic management
controls.
3. Level 3 (Defined): The organisation satisfies all the requirements of Level 2. At this maturity
level, the software development processes are well defined, managed and documented.
Training is imparted to staff to gain the required knowledge. The standard practices are
simply tailored to create new projects.
4. Level 4 (Managed): The organisation satisfies all the requirements of Level 3. At this
level quantitative standards are set for software products and processes. The project
analysis is done at integrated organisational level and collective database is created. The
performance is measured at integrated organisation level. The Software development is
performed with well defined instruments. The organisation's capability at Level 4 is
"'predictable" because projects control their products and processes to ensure their
performance within quantitatively specified limits. The quality of software is high.
5. Level 5 (Optimising): The organisation satisfies all the requirements of Level 4. This is
last level. The organisation at this maturity level is considered almost perfect. At this
level, the entire organisation continuously works for process improvement with the help
of quantitative feedback obtained from lower level. The organisation analyses its'
weakness and takes required corrective steps proactively to prevent the errors.' Based on
the cost benefit analysis of new technologies, the organisation changes their Software
development processes.

4. (a) Explain the terms “Black Box Testing” and “White Box Testing”.
Answer :
White Box Testing
White Box testing is also known as structural testing or glass box testing. Its goal is to test the
internal code of the software. It tests the program at the level of the source code. Here, the tester
has the knowledge of the actual source code of the software and what is tested, is the inner
structure of the program. Test cases are written with the knowledge of the logic of the program. We
are only concerned with the testing of accuracy of the logic of the program. We do not focus upon
the requirements of the software.
We may state that white box testing is the deep and detailed inspection of the logic and structure of
the source code of an application or program. Here, the main focus is to exhaustively execute the
program several times, with different inputs to ensure that each statement of the code is executed
and tested .
In white box testing, all the test cases are written with the knowledge of the internal structure and
logic of the code to make maximum test coverage of the code. This is primarily done by the
programmer or developer who develops the code. It is a first step to testing and to ensure that what
is implemented in the code promises to execute accurately.
An exhaustive white box testing:
 Guarantees that all independent paths-have been executed.
 Executes all logical decisions on their true and false sides.
 Executes all loops at their boundary values and within values.
 Executes internal data structure to ensure their validity
Example-1
If we have a line of code as below:
If(age >= 18) 0
For testing this code, we must run the program to test three different test cases,
T1: when the value of age is less than 18,.
T2: when the value of age is equal to 18
T3: when the value of is greater than 18.
And for each test case we must ensure that the right code is executed.
Example-2
if - then - else type of decision making code is tested for the true as well as false value.
If (choice == 1) {
}
else If (choice == 2) {
}-
else If (choice == 3) {
}
In the above case, we must test it for all the cases for the choice value i.e. 1,2, and 3.
Example-3
For a loop structure like
for (counter = 0; counter <= 10; counter++) {}
We must test it separately for boundary values of loop variable counter i.e. 0 and 10. We must test
for within values like 1 to 9:
Black Box Testing

Black box testing is also known as functional testing. The sole purpose of black box testing is to test
the application or software from its functionality point of view. In this types of testing, the software
is tested to check whether the software fulfils all the specified requirements. In Jack box testing, a
tester is not concerned about testing the logic of the program. The' internal details of the program
are not known to the tester. In this types of testing, the software is like a black box to the tester
where internal details are undisclosed. The tester only tests the functionality of the program by
supplying an input and observing the output. As already stated, an application or software is
developed to fulfil certain objectives or requirements. Black box testing is a detailed inspection of
the software functionality against the already specified requirements for which it is developed. The
test cases are carefully written for each and every requirement specified. We may agree that black
box testing verifies a software to ensure that it does exactly that, which it is required to do.
Example :
Suppose ,we are required to build software for purchasing books online. The
simpler r quirements can be stated as
Requirementl - User should be able to login to the website
Requirement2 - User should be able to see books catalogue
Requirement3 - User should be able to place an order
R uirement4 - User should be able to make the payment
Reqnirementf - User should be able to logout
Now, developers will write the complete code for implementing all the above stated five
requirements. A tester will then test the software to see if the developed software meets all the
stated five requirements. For this, a tester will write the test cases for testing each requirement.
Requlrement 1 :User should be able to login to the website
For this requirement, a basic set of test cases would be something such as:
(b) How will you ensure that the software developed by you meets the Quality benchmarks ? Define
the term “Software Quality”.
Answer :
SOFTWARE QUALITY ASSURANCE (SQA)
The term "Software Quality" refers to conformance to explicitly stated requirements and standards,
as well as implicit characteristics that customers assume will be present in any professionally
developed software. The SQA group must look at software from the customer's perspective, as well
as assessing its technical merits. Software Quality Assurance controls variation among products.

Software engineers are concerned-with controlling the variation in their processes, resource
expenditures, and the quality attributes of the end products. The activities performed by the SQA
group involve quality planning, oversight, record keeping, analysis and reporting. An elaborate
definition of SQA can be given as the following:
A systematic, planned set of actions necessary to provide adequate confidence that the
software development process or the maintenance process of the software system product
conforms to established functional technical requirements as well as with the managerial
requirements of keeping" the schedule and operating within budgetary confines.
Software Quality Assurance (SQA) consists of a means of monitoring the software
engineering processes and methods used to ensure quality. It does this by means of audits
of the quality management system under which the software system is created. These
audits are backed by one or more standards, usually ISO 9000.
It is distinct from software quality control. Quality Control (QC) is a set of activities (including
reviewing requirements documents, and software testing) carried out with the main objective of
withholding products from shipment if they do not qualify. Quality Assurance (QA) is meant to
minimize the costs of quality by introducing a variety of activities throughout the development
process and maintenance process in order to prevent the causes of errors; detect them, and correct
them in the early stages of the development. As a result, quality assurance substantially reduces the,
rate of non qualifying products. Software quality control is a control of products, software-quality
assurance is a control of processes.
5. (a) In Object Oriented Design, list the common utility objects and criteria for identifying
utility objects.
Answer :
Utility objects are often provided in a framework to address specific utility functions.
They are often used as "helpers" by the rest of the objects.
Criteria for Identifying Utility Objects
The following are the key criteria for identifying utility objects:
 The object should act as a helper to other framework classes.
 The object should provide a re-usable context-independent utility throughout the system
 The utility provided by the object should be used across various layers.
Common Utility Objects
The following are the list of utility objects generally used in a typical enterprise
application:
 CachingUtility: For handling the caching requirements
 LoggingHelper: For logging info, debug and error statements
 FileReaderUtility: For reading the required files
 ResourceLocator: For providing the URL for a given resource
 BuildUtility: For handling build activities
 EncryptionUtility: For-encrypting/decrypting the values as per enterprise standards
 ExceptionHandlerUtility: For handling exceptions
 EncoderUtility: For performing HTML encoding/decoding
 StringConverterUtility: For converting string into appropriate display formats
 MultiLangUtility: Forgeting the language specific resource bundle for a given key
 ConfigurationHandler: For handling different configuration files
 ValidationUtility: For performing required field validations

(b) Explain various Debugging strategies.
Answer :
Debugging Strategies
Effective debugging involves deep knowledge of underlying systems and processes and
creative thinking; it involves careful generation of hypothesis and testing it. Some of the
most commonly used strategies for debugging are listed below:
• Debugging by cause elimination: This strategy is adopted for complex issues that
involve different layers and components. Here, we systematically eliminate one
layer or component at a time starting with the layer/component that is has most.
For instance, if there is an issue probably defective with the page performance, we
start eliminating various components on that page followed by removing all
interfacing components. If a page is integrated with number of data sources, an
issue with one of those data sources may hog the entire page.
• Combination of test data and conditions: This strategy is used when there are
multiple causes for the defect. We try out various permutations and combinations of
the variables/test data and conditions till we identify with certainly the exact set of
variables that can accurately reproduce the issue. For instance, if a function call with
three arguments rises an exception, we try combinations of three arguments to
understand the exact argument that is causing the issue.
• Memory profiling: This strategy is normally followed for memory related issues. A
profiler tool is used to analyse heap memory during program execution. This would
give insights into components consuming more memory and the ones which are
orphan/not garbage-collected. With this information we can then deduce the cause
for memory leak issues. This technique also involves analysing memory/thread
dumps.
• Step-wise debugging: This is another technique which is often carried out with the
help of Integrated development environment (IDE) tools, In this technique; we start
the program in "debug mode" wherein, we can control each step of program
execution using IDE. We can then "step-in" and "step-out" each line of code
inspecting values of various variables. This helps us to get the exact method, line and
variable value where the defect has accused/occurs.
• Call tracing: This is a top-down approach wherein, we trace the call from the top-
most component to the root data source. We examine the return value at each level
to isolate the code that is the cause for the issue.

IGNOU BCS-051 Software Engineering December 2022 - Exam Solutions.docx

More Related Content

What's hot (20)

Similar to IGNOU BCS-051 Software Engineering December 2022 - Exam Solutions.docx (20)

Recently uploaded (20)

IGNOU BCS-051 Software Engineering December 2022 - Exam Solutions.docx