Corrective maintenance:-   All problems in PTW is all about the lack of the IT department  because IT department test data files thoroughly ,test the system  properly and according to this prepare the right document reports .So PTW must arrange IT department for the system.

Adaptive maintenance: – This maintenance increases the efficiency of the operational system as well as makes easy the using of the system. It adds new abilities and features in the system by changing the business atmosphere like putting the new web based system and IT staff. This staff analyses, design, test and implement the system. This system is the need of the PTWIS.            

Perfective maintenance: – PTW should adopt this maintenance as they store different type of data in different softwares. So it reduces PTW effectiveness .This maintenance will help to store data in one software and also improve reliability of the system. In spite of this, this is a very cost effective maintenance. So PTW should use this.

Preventive maintenance: – This maintenance tells the problem area. It works like the Perfective maintenance .It enhances the user satisfaction , decrease downtime and total cost of ownership.

3.

• Data flow diagrams
• ERD
• Traditional and object oriented approaches for system develpoment life cycle.

4. I want to become data designer in any company.

5. This course has given me the knowldge of website ,data designing ,implentation problems and changing the cuurent system and use new system .All these skills and knowldge will help me in my future when i will become a data designer in a company.

Direct cutover: – Direct cutover contains the immediate transformation from old system to new system. It is not very costly system as IT group controls and preserves only one system at a time during this approach. System cutover occupies some menaces as a lot of complexities produce when a system goes into operations. This problem come up from the data situations that were not experienced or estimated or from the inaccuracy which is caused by the users or operations .Although all approaches has an implementation troubles but direct cutover method involves high risks compared to others. This system applies software package for implementation as it has a less risk of failure. From the above write benefits and risks of this system, this not the suitable change for PTWIS.

Parallel operations: – This approach is very slowest as it needs both new and old systems simultaneously for a particular period of the time. Data is input into both systems but output is produced by only the new system .The chief benefit of this approach is that it has lower risk means that if new system is not work correctly then firms can use old system beneath this approach. It is easier to determine that new system is work properly or not because output from two systems is compared. But these systems have some disadvantages as it is an expensive and a company require new employee. Moreover running two systems at the same time is the burden on a company.

Pilot operations: – It is the combination of Parallel approach and Direct cutover approach. In this approach, implementation of new system is done in the chosen sites of the company in spite of implementation in entire organisation .It condensed the danger of system failure compared to direct cutover approach.

Phased operations: – It comprised the accomplishment of new system in stages, sections or subsystems .These systems are implemented by the above three approaches. The leading benefit of this system is that the failure of system is not related to the whole organisation but it is related to the particular section of the organisation.

From the above discussion of all operations which are used to change from one system to another system we see that phased operation will be the excellent approach for PTW because by this approach PTW will implement the new system in sections rather than making changes in the whole system. Moreover this system will not be very expensive for PTW because they will change section wise section in spite of the changing in the whole system. Moreover it will take a little time.

Journal-Journal of Information Systems Education

Author-:Pavle Bataveljic,Marian Eastwood and Heinz Seefried

Year-2006, vol.17, iss 3. PP 6 of 267(Online proquest).

This article discusses the developement period of both these two approaches as structured approach is developed beneath the control of  structured programming paradigm.This approach basically consists data flow modles. These modles are also used by the object oriented approaches.After that it will describes the characterstics of both approaches.

 Article-Object -oriented analysis and design :A new approach to system developement

Journal- Journal of Systems Management

Author- Garceau,Linda R, jancura,Elise G, Knesis, John Year 1993.vol.44, iss.1 pp .8 of 25 (Online Proquest).

This  article especially examine the object oriented approach and its importance in SDLC as well as compare it with structured approach like it improves flexiibility ,increase productivity ,makes easier to modelling and reuseability of codding. OOAD is a successful interface, computer aided design and engineering applications.It describes that as structured and other classical approaches mainly focus on development processes whereas object oriented approach concentrares  the defenition ,structure  and use of data in SDLC.

System analysis and design withn UML version 2.0

Writer-Dennis , A, Wixom, BH & Tegarden,D

Year -2009

Publisher- John Willey & Sons , U.S.A

 It explains some problems  of object oriented and traditional approach  in object based lanaguage.As well as their differences. It demonostrates  that rapid application developement methodology and primary differences between RAD and OOA and they  decompose the problems within traditional and object oriented approach.

The main similarity between  traditional and object oriented approach is that both are used the same logical designs  of previous stages for SDLC eventhough object oriented approach is used more modles but these are same to the taditional approach’ s model  and also both approaches are gone through common series of the phase of  system develpoment life cycl

Q. Name one way that the traditional and object-oriented approaches to information systems development are different. Explain how they are different.

Traditional approach is also referred as process centred approach because both data and procss are behave differently in this , but in object oriented approach these both are combined. In traditional approach processes are work as ‘one-off’  rather than continuous. It is also followed  the top to down approach because in it higher levels of designs are broken into smaller parts by using the processes. It is called  decompositionn. But  on other side  object oriented approach uses  bottom up approach which has a freedom to use data and processes.

http://www.cs.uct.ac.za/mit_notes_devel/SE/Latest/pdf/Chp09.pdf

Process number: 1

Purpose: Check DVD stock and tells customer about DVD stock and gives information when they can get it.

Input data flows:Accept order and check DVD and also keep details of payment.

Output data flows: Reject order if DVD not available or give borrowed DVD to customer.

Process dercription: Give DVD to customers and receive money.Staff can also reject customer.

Q2.  What is the object-oriented approach to systems development?

Q3.What textbooks, journals and/or websites might be useful to search for articles about Comparing and contrasting the traditional and object-oriented approch to     system developement?

Ans. We can use google website to find online  books,articles about object oriented and traditional approch.Furthermore journals lije Journal Of Information Systems Education{Carte,TA,Japerson,JS &Cornelius,MK 2006,vol.17,iss. 1,pp.55-63(Online ProQuest) can be used to compare  and contrast these two approchs.