ITC508 Architecture And Design Of The Airline System
In this recent scenario, each and every industry desires to improve its sustainability and to do so, inevitable phase, change need to be accepted. Only then, it would enhance its prosperity and demand in the market. This assignment tries to highlight the effect of change within the functional and non-functional operations of an organization. And in what ways, a change need to be implemented in order to make it effective in all regards so as to reduce the functional errors in a significant manner.
In order retain successfully in this contemporary scenario, the airline industries need to offer highest attention towards innovation.
This is done in order to reduce the challenges of the current situation efficiently so as to augment the reliability and position. Similarly, the airline industry mentioned in the case also needs changes in the hardware, software, operating system as well as the unique communication techniques.
Since, it is a customer centric organization, therefore it need to act as per their requirements. The information system of the airline also needs to include varied types of essentialities such as check-ins management of employees, marketing the organization services etc.
The prime intention behind such types of changes is to control and manage the operations of the flight in an efficient manner. Doing so might present advantageous in amplifying the satisfaction rate of the customers thereby boosting the profitability and net income. In concern to this statement, Conallen (2015) denoted that changes need to be introduced after proper acceptance of the users.
Only then, it would present pessimistic aspects towards the improvement of the brand image and market share of the brand. This may be possible only if the employees get indulged in training procedures so as to understand the pros and cons of the system in an efficient manner.
Then, both functionality and non-functionality functions may be easily and efficiently managed and supervised by the newly adopted information system of the recent era.
Contrary to this, Arrington (2014) signified that improper acceptance might hamper the prosperity of the system. As a result, the trust and faith of the employees and the customers would get disturbed that can lower the popularity of the airline brands.
Therefore, in order to reduce any sort of grievance while introduction of the change, proper monitoring and supervision by the higher authority is essential. It would not only minimize any criticism and objection but also magnify performance of the airline industry.
The case study technique is considered as an efficient procedure for the users or the individual in order captivate their interest and attention.
This may be possible due to the presentation of varied positive and negative effects with the use of flow charts, diagrams and sequence charts. Other than this, domain model uses case study as a conceptual framework in order to implement both behavior as well as facts and figures.
The key aspect of introduction of such types of case study models is to improve the positive results thereby diminishing the scope of errors within it. In term to this statement, UMl (2014) mentioned that case study approach is considered as the prime requirement within the domain model, without which it may not be introduced accurately.
This is because; case study acts as an interface within the requirement and design analysis phase of the domain model. Due to this, it is recognized as the prime requirement of the domain model in order to make it successful in all aspects.
However, in order to do so, proper training is also extremely essential. Only then, it would prove effective for the users to adopt the introduced changes effectively. Against the latter statement, Leffingwell (2015) argued that failure to incorporate the training programs accurately, might create varied types of problems within the organization.
Since, the techniques required to use and operate the model in an accurate manner prevails within training activities. Thus, through training, the ways, by which the program or model would interact with the users and the environment, may be easily analyzed.
Hence, the scope of errors would lower thereby extending the success ratio.
Other than this, case diagram also helps in the development of a specific bond within the system and the users. Along with this, both external and internal requirements also need to be focused in order to reduce any sort of discrepancies.
Due to this, case diagram or model is also recognized as behavior diagram (Kalpia, 2015).
Users (system boundary)
From the UML domain diagram, it may be clearly identified the check in and check out time of the consumer, the flight departure time, flight number, destination, booked class, payment mode etc.
Thus, if the name of the customer just entered with the system, then it will present data and facts of its entire journey (Conallen, 2015). Whether, the client is happy or not is also mentioned within the domain UML model so as to examine the effectiveness rate.
Apart from this, the reason for lack of reliability is also mentioned within the UML design so as to mitigate it easily. But, the entries need to be made accurately, by the employees in-charge.
If it is not entered exactly then it may prove detrimental for the management of the airline industry to detecting its position in this competitive scenario.
In this age of advancement, inventive approaches need to be implemented within each and every parts of an industry. Similarly, in the case study, the airline industry requires augmentation in both function and non-functional areas.
As per question1, hardware, software, operating system needs development. Other than this, unique communication techniques are also another region that needs to be superior so as to extend the position of the airline industry.
In addition, the updated information system may also include the efficiency to increase the check-ins and check out facilities of the customers and employees. Marketing, financial operations, employee management etc might also be easily controlled through information system.
Contrary to this, Bittner and Spence (2013) described that failure to incorporate such type of functions, might prove troublesome for the flight industry. It would not be able to supervise and handle the functions in an appropriate manner and hence the reliability and gratification would get lowered.
The deign activities are:
- Check in
- Customer database
- Name of the consumer
- Age and date of birth
- Passport number
- Number of travel
- Booking class
- Check out
- Time of entry
- Handbags (if any)
- Payment (Y/N)
- Gate management (maximum use)
- Marketing services
- Pleasure rate (Y/N)
- Contentment (Y/N)
- Complementary food services (Y/N)
- Any other service required (Write :……)
- Payment options
- Good (card/cash)
- Bad(card/cash) (Bittner and Spence, 2013)
- Fair (card/cash)
- Employee management
- Time of entry
- Time to leave
Each of the above mentioned aspects would be entered within the design activity of SDLC and it would include the success of the information system. The updated procedure need to be inculcated effectively in order to make it accurate in all regards. If not, then it may create varied types of unknown errors within the system in the long run.
The system vision document is described below:
Purpose: the prime aim of this vision document is to register the requirements of the information system of the airline industry. With the help of this document, the underlining ides gets entirely cleared.
Varied types of changes may also be possible with the help of the vision document and it assists the management in its design phrase. If it fails to implement the necessities accurately then it would prove problems in the coming era (Arrington, 2014).
Project overview: the introduced information system is essential to improve the gratification of the customers thereby enhancing the profitability and trust. To do so, various features are identified such as check in, check out, travelling time, ticket number, class, payment etc. So that, not a single information is left to the known from the customers and the travelling would become happier and easier.
System description: the details of the clients may be maintained easily with the use of UML and case use models. This may prove effective in inculcating each and every facts of the patron efficiently within the system. As a result, not a single fact would remain out of focus from the management perspective and this may be valuable for the employees.
System features: the features may be incorporated by the end users only. The management may edit the facts and the staffs engaged are liable to put the facts in it. If any wrong fact is given then it would create distress in the coming era.
Login details: the users and the customers need to maintain login details. A specific password and user-id is offered to login to it in order to make it effective. If the password is not appropriate, then it would not work accurately.
|Activities||1st Week||2nd – 7th Week||8th– 11th Week||12th -15th Week||16th – 19th Week||20th – 23st Week||24nd – 25rd Week||26th week|
|Pre-investigation of the requirements||•|
|Evaluation of the data||•||•|
|Implementation of the facts||•||•|
|Examination of the facts by staffs||•||•|
|Analysis and interpretation of facts||•||•||•|
|Training to the users||•||•|
The above presented time scale need to used in order to make the process of introduction accurate. If it is not followed, then it may create extreme trouble in the coming age and the rivalry may not be retained.
After analyzing the entire study, it may be revealed that information system is considered as the lifeline of any firm. Bit it need to be implemented effective so that, the customers may become contended with this. Best services and products may be offered to the consumers as well as the work load might be diminished entirely. Only then, the experienced employees may be retained and the competitiveness may be boosted. The position and prosperity of the firm may be enlarged with the use of such automated information systems.
Arrington, C. T.(2014). Enterprise Java with UML – Page 18. Usa: Sage learning
Bittner, K. and Spence, I. (2013). Use Case Modeling – Page 82. Usa: Routledge
Conallen, J. (2015). Building Web Applications with UML – Page 162. Usa: Sage learning
Kalpia. S. (2015). Academic Foundation`S Bulletin On Money, Banking And Finance Volume of information system. Usa: Oxford
Leffingwell, T. (2015). Managing Software Requirements: A Use Case Approach, 2/E. Usa: Routledge
UMl. (2014). UML Use Case Diagrams. [Online] Available at: http://www.uml-diagrams.org/use-case-diagrams.html [Accessed on 24.4.2017].