Contents

Part 1. 3

Introduction. 3

Enterprise Architecture Framework. 3

TOGAF EA FRAMEWORK. 4

Dynamic Software Development (DSDM). 5

Critical Analysis. 5

Delicious Bookmarks: 6

Conclusion. 7

Reference. 7

Part 2 and Part 3. 8

Design for the maintenance of Aircraft Applications. 8

Functional and Non-Functional Requirements. 8

Entity Relationship Diagram.. 9

UML Class Diagram.. 10

Use Case Diagram.. 12

Patterns for aircraft maintenance. 14

Design class diagram.. 16

Design decisions. 17

Screenshot of Software Run. 18

Research. 22

Conclusion. 23

Statement of Functionality Implemented. 23

Reference. 23

COMP1605. 24

Enterprise Patterns & Frameworks. 24

Record of demonstration. 24

Part 1

Introduction

The architectural framework of TOGAF provides a better information system for developing a specialized solutions for security and testing. This helps in covering the different aspects of business architecture. The process and the components of information are based on holding all the major supporting structures which can set up a related flow of usability and accessibility factor (Svee, 2015). The Enterprise architectural domain encompass different figures primarily based on the well-defined needs of the business. The major concern of productivity and all the business risks patterns are mainly based on the need to emerge the enterprising change in the organization. The technology needs to settle up the plans to accelerate and contribute towards holding a better technology architecture.

Enterprise Architecture Framework

As per the analysis, there are two issues related to the complexity of system and the business alignments which are helpful in making up the entire IT system. The cost effective patterns work on handling the entire architectural framework which emerge and follow the different enterprising solutions like TOGAF.

TOGAF EA FRAMEWORK

The driving of organization in order to improve the factors are based on architectural governance that commence with the architectural solutions. The running process needs to match with the multiple inputs and distribution patterns which provide a way to come up with the transformation ideas in order to achieve maturity. The coordination response escalates to change the strategic architecture with different functionality (Cabrera et al., 2015).

The DSDM is not able to incorporate all the understanding which come under performing and implementing a wider range of enterprising architectural program. The factors depend on the resource availability and the guidance which is based on the sizing and complex model build up. There are different approaches which lead to an enhancing process change in architecture:

1. The factors which depends on the processes of different frameworks are based on meta-structure modelling that constrain from adding bureaucracy (Freitag et al., 2015).
2. There is a need to work on all the activities and link with the enterprising solutions which can support and analyse all the important purpose for high level business implementation.

There are changes in the half solution degree pattern which describes all the frameworks as per the recommendation planning. The ADM (Architectural Development Method) works towards holding all the important plans which can provide a better process of multiple and consecutive planning in a closed loop. The purpose of setting up the architectural EA vision is based on creating a first cut description which holds to settle all the production to present the architectural framework.

Dynamic Software Development (DSDM)

The focus of this agile method to provide access to different methods which will emphasize to handle all the software development. The work is divided into three aspects of projects, its life cycle and the projects which are post related. There are patterns of DSDM which are based on the development and working on the techniques like Timeboxing, MosCoW, testing, the workshops, modelling and the management configuration. The buildup and maintenance is based on the scalability and the reusability patterns.

Critical Analysis

As per the agile software development, TOGAF has been the main to be constructed under the EA framework. The Scrum is an agile software which direct to define systems based on the increment and iterative nature. There are different levels of cycles which concern to handle the services of organization and build up enterprising functions with the requirement to set a proper job. The services and the change in alignment which is done to collaborate the roles. The TOGAF and SCRRUM have been under the enterprising architecture area which focus on the EA framework. The building up of all the admissible points are adapting and time consuming with the cost effective patterns. There is no possibility of short time durations for any constraints.

Conclusion

There is a need for delivery of different applications and architectures. This will help in analyzing the business gap which includes current planning with the deal to deliver the drafting architecture to actively produce different viewpoints (Cvetanovic et al., 2015). The end-to-end process needs to come up with the organization of different methodology and business model languages which quantify to change the pattern of software lifecycle. The analyses is based on demanding a rise in surrounding and combining with different infrastructure technology setup.

Reference

Freitag, A., 2015. State-of-the-Art of EA Management in the Context of M&A. In Applying Business Capabilities in a Corporate Buyer M&A Process(pp. 37-64). Springer Fachmedien Wiesbaden.

Cabrera, A., Abad, M., Jaramillo, D., Gómez, J. and Verdum, J.C., 2016. Definition and Implementation of the Enterprise Business Layer Through a Business Reference Model, Using the Architecture Development Method ADM-TOGAF. In Trends and Applications in Software Engineering (pp. 111-121). Springer International Publishing.

Svee, E.O. and Zdravkovic, J., 2015, June. Extending Enterprise Architectures to Capture Consumer Values: The Case of TOGAF. InAdvanced Information Systems Engineering Workshops (pp. 221-232). Springer International Publishing.

CVETANOVIĆ, S., VELJKOVIC, D., NIKOLIC, B. and DOMAZET, D., MODELING UNIVERSITY METROPOLITAN ONLINE LEARNING SYSTEM ARCHITECTURE-THE TOGAF/ARCHIMATE WAY.

Part 2 and Part 3

Design for the maintenance of Aircraft Applications

The development of system are based on meditating and working to build up a better prototype. The software engineering pattern trails to handle the analysis and designs with the achievement by following the logical, structural, behavioral and the integrations. The Unified Modelling Language is in oriented manner where the tools are set to provide a better interface structure for different conceptual diagrams.

Functional and Non-Functional Requirements.

The functional requirements are:

1. To set up a login page which can be same for the users to login and check into the database system for the authentication and providing the details on the home page.
2. There is an error message on the unsuccessful login in the page. The engineers can view and match with working to manage profile and handle the status with qualifications.
3. The administration needs to add a new job portal to change the status of duty.
4. The qualification of engineer match with the required one to add job else an error message.
5. The super admin can add the administration.
6. The job assigned then automatic change to work in progress.
7. The system needs to provide options to administrator to change the status of job as completed.
8. The logging should be stored into the database for every action.

 

The nonfunctional requirements are:

1. The system needs to provide and load the data stored in the database format.
2. The system is user friendly to all users.
3. The system should try to maintain all the extensions and durability.

 

The user database has the username, password, first name and last name. Username is the primary key here.

The crew database is for the crew group, with crew name and description.

The crew member database is for the members of the crew, with primary key as member name, and shift day and time, and crew name as foreign key.

The emergency database has emergency ID as primary key, and emergency location and crew needed, for the database.

Cardinality:

1. Multiple users can register via registration page.
2. One crew has multiple crew members.
3. One crew member can be involved in one emergency at a time.
4. User database contain details of all crew members, crews and emergencies.

The index page is the interface used by admin to log in. A signup page is also provided to the user, to register themselves. The user manager is the backend of login page. The authenticator authoresses the sign in operation using java. After logging in, the user can register crew members, register an emergency, generate reports or register crew groups.

Assumptions for the class diagram:

1. There are users in the system: Super Admin, Administrators and Engineers.
2. The requirements of Super Admin and in USER table and can be assigned to all other administrators.
3. The job needs to be worked depending upon the qualification.

The User Class is a parent class and work on the user interface pattern by using the users assumed. They can log into the system and the class is inherited. The engineers can add and work on the administrator which means to handle the system and work on the assignment. The Administrators and Engineers have a composition of relationship.

The admin has been provided with the feature with registering the user, logging in, emergency management, crew management and report generation.

A crew member has access to log in, to check the status of his details like shift time, emergency etc., and to be able to check emergency management.

Use Case Element	Description
Use Case Name	Register
Actor	Admin
Precondition	No precondition required
Basic Flow	Enter credentials Submit form
Alternate Flow	No alternative flow

 

 

Use Case Element	Description
Use Case Name	Login
Actor	Admin Crew member
Precondition	Already registered
Basic Flow	Enter credentials Submit form
Alternate Flow	Wrong credentials entered

 

Use Case Element	Description
Use Case Name	Emergency Management
Actor	Admin Crew member
Precondition	Already logged in
Basic Flow	Emergency location Crew needed Submit form
Alternate Flow	Move to homepage

 

Use Case Element	Description
Use Case Name	Crew Management
Actor	Admin
Precondition	Logged in
Basic Flow	Crew name Description Member name Shift day Shift time Submit form
Alternate Flow	Move to homepage

 

Use Case Element	Description
Use Case Name	Report generation
Actor	Admin
Precondition	Logged in
Basic Flow	Emergency location Crew name Member name Submit form
Alternate Flow	Move to homepage

 

 

 

Patterns for aircraft maintenance

 

The designing patterns work on the molding of development. This works on extensively handle the designing systems for making it more readable. It is a good work to work on different design schemes which will force the patterns to formulate the development code to a more complex extension.

The formulation is based on:

1. Model View Controller (MVC) pattern

The entire pattern is important to take care of the system where the aircraft maintenance will help in handling the applications controlled by the users of MVC patterns.

The Model try to represent an object or JAVA POJO which works to carry on a logic with the updation of the controller on any change.

The View represents the visualization of the data which a model contains.

The controller is based on Model and View. This is important for the flow of data which updates the view when there is a change in data.

The MVC works on handling the user interface class which separates the presentation and try to increase the flexibility depending upon few dependency. The control is maintained using the single controller and works on the representation of all the functionality.

 

 

 

1. Data Access Object ( DAO) Pattern

This works to take care of classes or interface which interact and perform the functionality of database. There are classes which allow to handle the single class systems and work on the open connection to perform the tasks with the development made and the changes enhances.

1. Front Controller Pattern

It works on handling the requests and the application and route for appropriate view. There are:

• The login which works on the use case diagram which can properly access the system using the super admin, administrator and engineer. The users need to handle the login page which will direct to log in and direct to view based on user type systems.
• The log is for handling the aircraft maintenance application where every action is performed under the front controller to perform as per the application.

 

 

 

Design class diagram

 

The work if based on taking care of the Unified Modelling language in different object oriented features which work on the bases of design class diagram. Some of the methods are:

1. The Home Controller design

This works on taking care of the login page which is controlled by the account controller and needs to direct to the appropriate viewing pattern.

1. The account controller design class diagram

This will handle the controller login process and adding administration process if the super admin and engineer would work with the administrator login. There are DB Model class based acts which are important to interact with data base to perform different functionality.

1. Qualification controller design

This works to take care of the administrator to add qualifications to the system and work on using objects of DB Model to store into database.

1. The Job Controller class Diagram:

It is important to allow administration to add job, view and work on updating status to complete the job Model. The objects are there for user validation and to handle the engineers to administer depending upon the requirement and qualifications.

1. Log controller

There is a need to control all the actions and work on using the objects which will try to add the details of all the Log and lists the log.

Design decisions

 

The development process is based on using the prototype models which are achieved using different logical and structural framework. The tools are built which handle the functional requirements like the login details for users and authentication of database system. The view is based on administrative services which can easily quantify to appropriately work towards changing the work in progress (Bakar et al., 2015).

The non-functional requirements include the durability of the working system along with handle the system which is based on solving all the user friends’ issues. The work to carry out with the user entity and other relationships is based on using three types of system: Super Admin, Administrators and Engineer.

Research

The user tries to work onto logging the system and work on maintaining the applications. The critical research is mainly on using the SCRUM for the development practice. The life cycle is based on the organization service which needs to provide all the important enterprise architecture for a better framework. The commitment to supply with a unified liable includes the use case name and actors for the assigned job patterns. The inclusion of cases enter into accessing the data which is based on the formulation and development (Kirikova, 2015).

1. The model of view controller pattern.

This pattern is based on maintaining a major control over all the MVC system that sets up to control the change in data. The visualization processes of the data models the controller which works on the Model and View functionality.

With the major dependency, the representation is based on creating an interface of class which can interact with all the database functionality and try to allow the patterns to meet an open connections which can perform the functionality for building up a secured system layout.

1. The data access of object pattern.

This focus on developing all the changes which connects with building up secured system and deal with the login of different accounts. The administration matches with the requests and applications to appropriately view the relevant patterns of accessing and redirecting the system.

As per the performance, the major focus is on controlling the login system plan which redirects to handle all the Super admin home view and other login models (WEREWKA et al., 2015).

Conclusion

The process needs to match with the enterprising architecture to hold on the documentation and standards which establish a variety of ad-hoc means. There are no explicit governance which are important to match with the communication to process improvement in the architectural documentation. With the change in IT vision, there are linkages of the profile which are for establishing responsibility using the security infrastructure. The defined way tries to set up the business management procedure which can easily lead to an integrated approach to set up all the operating standards (Bakar et al., 2015). There are IT security patterns which document important changes in the quality metric and associate with the updation of business and capital investment.

Statement of Functionality Implemented

All the functionalities mentioned in the assignment has been fully implemented. (Level 1)

Reference

WEREWKA, J., 2015. Investigation of enterprise architecture and software architecture in relation to quality attributes in military applications.Szybkobieżne Pojazdy Gąsienicowe.

Bakar, N.A.A., Kama, N. and Harihodin, S., A SYSTEMATIC REVIEW OF ENTERPRISE ARCHITECTURE ESTABLISHMENT PROCESS.

Kirikova, M., 2015. Enterprise Architecture and Knowledge Perspectives on Continuous Requirements Engineering.