Advanced Diploma IT Systems Analysis & Design Assignment - Module 4

This assignment solution addresses key concepts in IT Systems Analysis and Design, focusing on object-oriented software principles such as abstraction, encapsulation, inheritance, and polymorphism. It explores how these concepts facilitate the design, testing, and maintenance of software systems. The solution includes a class diagram and sequence diagrams using UML to model system domains and processes. It also analyzes the suitability of serialization versus relational databases, providing arguments for and against each approach, and discusses the use of XML and XQuery for data representation and querying. The solution offers a comprehensive understanding of software design, database choices, and data representation techniques, supported by relevant references and examples. Furthermore, the document provides XML documentation, including an example XML file and explanation of XML validation, alongside a brief overview of XQuery technology. This assignment covers a broad spectrum of topics essential for IT systems analysis and design, providing a detailed overview of the concepts and techniques involved in software development.

Advanced Diploma in IT Systems Analysis and Design
Question 1.
a. Object oriented software concepts.
In 2016, Satzinger, Jackson and Burd, suggested that when developing object oriented
software abstraction, Encapsulation, inheritance and polymorphism concept are so
important to implement in those objects.
Abstraction.
Abstraction: Data is represented and how it is implemented is it is kept out of sight.
There two main type of abstraction of data which are datatypes and object abstracts.
Encapsulation.
When interface is made available to users but purpose how it’s inside operation is hidden from
access.
Encapsulation is keeping implementation of data by preventing their accessing and mutating.
Inheritance hierarchy.
Modeling objects with features which are related. For example vehicle most vehicle has same
main features example all vehicles have wheels, engine and steer. For this redundancy avoidance
is to bring concept of inheritance. Inheritance it is reusing code of a super type by subtype object
objects.
Modularity.
It is about logical and physical appearance of objects.
Self-Contained : "Agile & Autonomous".
It means a system is made up of small components. This small components helps in functioning
and performance of system. You cannot change any small component the system may fail to
function. So modification have to be done to whole system.
High cohesion and loos coupling is encouraged in modulation.
Polymorphism.
It is self-representation in different form with same naming and operation is different.
Polymorphism requires inheritance.
Object-oriented polymorphism means operating not in same method, depends on instances
being operated on. Polymorphism enhances internal arrangement of objects to be similar with
external interface.

b. Object oriented concepts facilitate the design, testing and maintenance of software
systems.
Design
Object oriented support inheritance where objects are reused. The aim of reusability of software
is to make production of software low by substituting development with recycle. Reuse is to
reduce the cost of software production by replacing creation.
When design system high cohesion is allowed and low coupling is discouraged.
Attributes which public are overridden and inheritance take place so the percentage of them is
important. Immutable attributes its percentage is note. When percentage of immutable attribute is
high it means they conform to encapsulation.
Testing.
Modularity is allow during testing software need to divide and conquer principle during
testing .Dived testable modules into small manageable tasks
Changes in operation of software;
Maintenance.
Faults are always repaired when there is failure.
Upgrade of hardware and software;
System reliability and performance is improved always
New software requirements keep coming in place while software is in use.
Question 2.
In 2016, Lethbridge and Laganiere explained that Uml class diagrams make work of programmer
easy because it indicate methods and attributes used on class.

Figure 1 below showing Class diagram of Domain system.

Question 3
a. Figure 2 below showing sequence diagram of all list of flight a passenger booked.
In 2016, Ian Sommerville, explained importance of using uml diagram in modelling .Uml
diagram help designers and developer to capture most important requirements of sytem.

b. Figure 3 sequence diagram below showing a book flight of passenger.

Question 4
a) The reasons why serialisation is not be suitable in the final design of the system.
Serialisable interface do not have methods and constants are not define so it is empty designing
something empty makes design difficult.
Serialisation is used for small systems because it uses small objects and memory is small. So
when storing big data or developing a system which holds big data serialisation is discouraged.
Serialization can be replaced by xml system, NoSQL database and relational database. Database
system holds a lot of data.
Serialisation’s assumes system sessions take short period of time to be alive. In real sense
persistence of data takes a long period of time for example weeks. This makes serialization not
good to use. Developer need serialized ID in sessions but most developer do not use id to
implement serialisable interface.
b) The arguments for and against using an object oriented database with this kind of
system.
Developing prototype.
In 2018, Pressman proposed that developing prototype at early stage help to capture
requirements from users and involves them during designing.
Prototype is developed to manage property of owner. Prototypes are mostly designs at early
stage of developing in demonstrating how final product will be and used to capture
requirement So prototype should be developed very rapidly and we use serializable objects
to store data unsteady of using relational database or any persistent system because will
take a lot of time to develop it and slow development.
Storing small objects for short period of time. Objects of owner1, owner2, owner 3,
property1, property2 and property 3 are stored on server application. Session persistence of
information uses serialization.
c) Explanation of decision taken to use a relational database with example and
problems would arise.
System will delay in development because a lot of time is required to created tables and
fields but system is required quickly.
Cost to design relation database you need money to buy software and employ someone to
develop Sqls.
Limits of fields of relationship databases.
System has small objects and handles small jobs so there is no need to develop a big
database.
d) Explain difficulties, suggestion and addressing using example from system
described.
Use serialization because system is small and holds small jobs.

JAXB technologies available use of operation which are low costs and reduce relational
problem . provide similar functions with a similarly low cost, while reducing some of the
problems.
There is no use of schema while using JAXB.Storages can be created from classes. When
JAXB is not important, there are a lot of technologies for example XML.Xml is middle
point between relational database and documentation.
Question 5
a). <?xml version="1.0" encoding="UTF-8"?>
<Library books>
<Book1>
<title> System Analysis and Design in A changing World </title>
< ISBN number > 13: 978-1-111-53415-8 </ ISBN number >
< authors >Satzinger, Jackson and Burd </ authors >
< publishing > Course Technology </ publishing >
< date > 6/4/2016</ date >
< edition > 10th </ edition >
< Volume present>2000</ volume present >
< Request time in past four years>1000000</ Request time in past four years >
</ Book1>
<Book2>
<title> Software Engineering. Practitioner’s Approach </title>
< ISBN number > 0-07-365578-3</ ISBN number >
< author > Pressman, S, Roger </ author>
< publishing > McGraw-Hill </ publishing >
< date >6/4/2018 </ date >
< edition >8th </ edition >
< Volume present>3200 </ volume present >
< Request time in past four years>30000000000 </ Request time in past four years >
</ Book2>
</ Library books >

b).Ensuring XML documentation is valid.
XML VALID Documents.
XML browsers checks for validity of XML documents, if associate schema of xml and
document type of definition are valid and compliant.DTD and xml schema should conforms to
document syntax. A valid xml document must have the follow.
For every XML document there should be a root element.
For every XML elements there must be a closing tag.
All XML tags are sensitive to case.
Nesting of XML elements should be proper.
You should quote ALL XML attribute values.
c). Brief overview of XQuery technology.
XQuery it is a query language which is used by programmers in getting extensible markup
language files .Understanding syntax of xquery is simple and easy.XM; documents are easy to
view relational database. XQuery is used by oracle, Ibm and Microsoft. Xpath are used by
Xquery.The relationship between Xpath and xquery is so close.X query 1.0 are got from x path
2.0.XPath queries are simpler than x Query.
Bibliography.
Books.
John W. Satzinger, Robert B. Jackson and Stephen D. Burd, System Analysis and Design in A
changing World (6th EDN Boston Course Technology 2016).
Ian Sommerville, Software engineering (10th edn, University of St Andrews, Scotland:
Pearson2016).
Pressman, S, Roger, Software Engineering. Practitioner’s Approach (8th edn, Inc., 1221 Avenue
of the Americas, New York, McGraw-Hill2018).
Timothy C. Lethbridge and Robert Laganiere,Object-Oriented Software Engineering: Practical
Software Development Using UML and Java (3nd edn., New York, McGraw-Hill.2016).