Keywords SOA-PMS, Project, Data warehouse, Data mining, Web based.

International Journal of Advanced Research in

Computer Science and Software Engineering

Research Paper

Available online at:

www.ijarcsse.com

Service Oriented Architecture in Project Management

Software

Mohammed Farooque Khalil Abdulnaser Rachid

College of Computer Science College of Computer,

Department of computer Science, Computer Science Department Jazan University, Jazan, KSA, Qassim University, Alqassim, KSA

Saudi Arabia Saudi Arabia

Abstract—Service Oriented Architecture in Project Management software (SOA-PMS) is used to collect the information from the different levels of software development process and different peoples involved in the project and product development., it monitors the entire software development life cycle and provide status and reports at the different levels, It maintain the details of the client and the developer interaction as all the documentation work is done by both the client and the software development team who are working on the client project and product. The information updating is done by the authorized person of the company who is in contact with the client and with the development team basically the project manager can manage all his developer’s activities and the client can monitor the project managers as well as the developer’s activities without wasting time and money for traveling. The client who is giving the project and product to be developed to the company can view the documentation that is done. Project Management Software (PMS) will be implemented using SOA i.e. Service Oriented Architecture, over the web.SOA would help to reduce the server load, where the process would be done on a different machine other than the server hosting the system, making the application more robust, in terms of supporting multiple users. Service Oriented Architecture in Project management software has various modules that perform various functionalities such as the Authorization, client information maintenance, project inquiry, proposal sending, proposal converted to project information, project planning and execution, add project details, add project modules, project testing, project testing details, history of the bugs can be viewed, project release details, pending issues details, user access granting, maintaining employee details

Keywords—SOA-PMS, Project, Data warehouse, Data mining, Web based. I. INTRODUCTION

SOA – PMS (Service Oriented Architecture in Project Management System) is a system, which basically monitors the SDLC phases using service-oriented architecture. Implementing SOA in PMS helps to reduce server load making multi-user access possible. The SOA-PMS will give you and your team greater real time insight into project requirements, and the inevitable changes of the scope that cross the boundaries of the distributed system. This Project helps you to monitor the various activities of an organization thus providing with the facility to produce greater output. It will provide various services to the different levels of software project and will provide services to the people involved in the different levels of project development lifecycle. It generates the various reports It will provide various services to the different levels of software project and will provide services to the people involved in the different levels of the project development lifecycle. It generates the various reports of the different activities that are done in the project as the client can view the daily report of his project that is given for the development. Project Management Software is used to collect information from the different levels of software development life cycle and provides status and report of the different levels, it will maintain the details of the client and the developer interaction as all the documentation work will be done by both the client and the software development team who are working on the client project/product, it will monitor the entire software development life cycle and provides status and report at the different levels, it will maintain the details of the client and the developer interaction as the documentation work will be done by both the client and the software development team who are working on the client project/product. The client has a tight control on the different parts of project product and also the client will get all the details of the project/details. The client gets a feedback related to the project /product and he needs to keep a track of all these details. The client can view details such as the daily status report or a weakly status report or a monthly status report of his project. The client also obtains the detailed information of his project which involves how many people are working on his project and also note their status. Thus in short the client has a complete monitoring control over his entire project/product. Monitoring and controlling the phases of Thus the entire software development life cycle can be monitored using SOA-PMS.

June - 2014, pp. 674-679

The phases of the software development life cycle monitored using the product SOA-PMS are:

1. Requirement Analysis 2. Prototyping 3. Design 4. Development 5. Testing 6. Documentation 7. Development 8. Maintenance

Fig 1: Software development Life cycle .

II. SYSTEM ANALYSIS AND DESIGN FOR PROJECT MANAGEMENT SOFTWARE

Requirements analysis and gathering; use cases, identifying the classes, sequence diagrams, state charts, activity diagrams, contracts, domain model, design collaboration and class diagrams, signatures, user interface design principles, human and organizational factors, physical environment, alternative, deployment; software quality assurance and change control. Software Project Management-Scope; estimation, scheduling, risk management, project control and monitoring, project planning documentation, work in teams. A data warehouse is a collection of project data, Reports, analysis, design, coding and testing these are club together to make a data warehouse. As a huge amount of data is stored in the data warehouse related to the clients project. There is a necessity of mining this data so as to produce the desired results that can be shown to the different stake holders. We will be mining the data from the different table of the database; the different table contains data related to one client’s project. The tables are as follows.

a. Client information management

b. Inquiry

c. Proposal (plan, application, offer)

d. Requirement e. Planning f. Designing g. Coding h. Testing i. Deployment

June - 2014, pp. 674-679 j. Maintenance MSSQL Database User Add Project Requirement Analysis Coding Testing Design Acceptance User User

Data Over View Diagram

Figure 2. Database Diagram for PMS

The above figure shows that there is a database named “Database.mdf” which contains number of tables. These tables stores huge amount of data related to the client’s project. The stakeholders get connected to the database through the web. Each user has a different perspective to access the data. The data warehouse contains all the data when the stakeholder requests for the data it is mined from the data warehouse and the relevant data is displayed to the stakeholder. The above data tables contain information which can be mined and displayed as per the stakeholders requirements hence mining of information is necessary for the huge data of the project. As the information on this topic is scanty hither to I have decided to investigate this topic Service oriented Architecture in project management software in more details. Project Management Software will be used to collect the information from the different levels of software development and different peoples involved in the project and product development. This software will handle all the activities starting from the -Inquiry by the client to the Planning, completion and delivery of the product made by the company to the client. All the activities will be monitored and will be documented which can also be viewed by the company who has made the product for the client along with all its details of the product and with information that was required in building the product and also it can be viewed by the client on the client side as the client will be able to view all the details of his product and also will be able to interact with proof with the team members working on this product.

The goal of Project Management Software is to produce a product that is delivered on time, within the allocated budget, and with the capabilities expected by the customer. Project management software is basically a properly managed project has a clear, communicated, and managed set of goals and objectives, whose progress is quantifiable and controlled and whose resources are used effectively to efficiently produce the desired product. When properly managed, a project usually has a communicated set of processes that cover the daily activities of the project, forming the project framework. As a result, every team member understands their roles and responsibilities and how they fit into the big picture, thus promoting the efficient use of resources.

Project Management Software will be used to collect the information from the different levels of software

development and different peoples involved in the project and product development. This software will handle all

the activities starting from the Inquiry from by the client to the Planning, completion and delivery of the product made by the company to the client. All the activities will be monitored and will be documented which can also be viewed by the company who has made the product for the client along with all its details of the product and with information that was required in building the product and also it can be viewed by the client on the client side as the client will be able to view all the details of his product and also will be able to interact with proof with the team members working on this product. The client will come to know the exact manpower employed and the time duration spend by each employ that is employed on his product development. So that there will not be any hiding of information from the company who is developing the product for the Client. The collaborative information, which will be gathered, will be visible to the client and the company who is developing the Product. Hither to the information on this topic is scanty thus it is decided to investigate this topic in more details so as to minimize the cost of the product developed and also to save the time required in the development of the project/product for any client.

June - 2014, pp. 674-679 III. OBJECTIVES OFTHESYSTEM

My objective behind this software is to develop a data warehouse which contains data of the software project starting from the client information management to the delivery and maintenance of the project, the entire SDLC of the project will be stored in the data warehouse as many projects are going on in the industry there is a due need of a data warehouse to store all the information of the project at a central location so that all the information when requested by any stake holder will be accessible at any point of time. Data mining can be performed on this data warehouse and relevant information can be displayed to the stake holder. With data mining and ware housing for project management we can move into the future without abandoning the past. Move into the future for the betterment of the information centralization of the project and thus getting the data access at any point of time. In this software I will be creating a data warehouse which will store the data of the project following data will be stored Client information, inquiry, proposal, project planning, design ,coding ,testing, deployment, maintenance of the projects. All this information will be accessed by the stake holders of the project as this information is centralized mining the data from the repository is very easy task. As and when the stake holder request for the information it will be mined from the repository and will be available on the stake holder’s browser as it’s web based project management software. In order to improve project management and success rates of such projects a life cycle is vital to the overall success of the project. A paramount determining factor in the success of data warehousing is the input of Stakeholders. Data warehousing is very unique to an organization, its business processes, Systems architecture and decision support needs. Project management for data warehousing allows for large amounts of user input and at all phases of the project. There are commercial software products tailored for data warehouse project management. A good project plan lists the critical tasks that must be performed and when each task should be started and completed. It identifies who is to perform the tasks, describes deliverables to be created and identifies milestones for measuring progress.

In this software I will be creating a data warehouse which will store the data of the project following data will be stored Client information, inquiry, proposal, project planning, design ,coding ,testing, deployment, maintenance of the projects. All this information will be accessed by the stake holders of the project as this information is centralized mining the data from the repository is very easy task. As and when the stake holder request for the information it will be mined from the repository and will be available on the stake holder’s browser as it’s web based project management software. In order to improve project management and success rates of such projects a life cycle is vital to the overall success of the project.

The major objective of project management software is to produce a product that will deliver the required data within the time and the allocated budget.

 To Ensure Projects are delivered within budget.

 To ensure the projects are delivered within scheduled commitments

 Deliver quality solutions.

 Reduced errors

 Improved effectiveness

 Appropriate risk management and internal controls

 Continuous process improvement via collaboration

 Implement project communication and oversight

 Implement centralized data storage

 Extraction of data as and when needed by the stake holder.

IV. SCOPE &LIMITATIONS

The scope to manage all organizational projects, not just IT projects. The project is to design a common platform for the project management where all the stake holders concerned with the project will add and view the data as and when it will be required. The scope is not limited to only to software projects related to companies but it can be extended to educational institutions also where the students of the institute can fill in the information related to their projects all the stake holders such as teachers who are guiding them can access this information and validate the students performance and completion of the students projects.

The various data extraction methods will be used to extract and display the information that will be asked by the stake holders.

Limitation

Inability to “stick” with the project scope: Project Management, by definition, is unable to commit to the original project scope due to constant change requests. Project Management acknowledges this with the formal integration of Change Management. This limitation causes a lot of problems, and is the reason why so many projects end up way over budget and many months/years late, sometimes even canceled or killed.

Inability to fully align the project objectives with the business/organizational strategy: By definition, Project Managers manage projects, not their organization. Although projects are usually initiated by stakeholders/executives with a clear relation and full alignment with the overall corporate strategy, Project Managers are incapable, by themselves, to make sure that their projects are kept aligned with the company’s strategy. In order to solve this limitation in Project

June - 2014, pp. 674-679

Management, Program Management was introduced as a higher layer of managerial control to guarantee and sustain alignment.

Inability to manage projects with unspecified budget and/or schedule: This is probably the biggest limitation in the traditional incarnation of Project Management. Imagine if, thousands of years ago, pyramid building was restricted to a budget and a schedule. Would the pyramids have lasted so long? Would they have been considered as marvelous wonders? Project Management imposes a budget and a deadline on any project and thus creates a major problem: All projects finishing on time and on schedule (and they are very rare) have their quality compromised (when was the last time you saw perfection in any project?). Resources are not allowed to give their best, gold plating is considered a bad practice, and resources finishing on time, regardless of the delivered quality, are considered heroes.

Dependence on functional management: Traditional (non-agile) Project Management is clear about the authority of the

Project Manager over the resources: he has none. It is the functional managers who own the resources: they have their

loyalty (resources are loyal to their functional managers as they’re the ones who report quarterly on their performance), they have their gratitude (most resources are hired directly by their functional managers), and they have their respect. The dependence on functional management is a major limitation in Project Management, as Project Managers are constantly at the mercy of both the functional managers and the resources (indirectly, for example, an excellent resource resenting the presence of the Project Manager might disobey him, while still being supported and endorsed by his functional manager), and they have to compromise, or “offer something” in return, just to get things done. Note that this limitation is almost negligible in highly projectiles organizations.

Following an exclusive methodology Project Management forces the Project Manager to choose and follow a methodology, be it the traditional (waterfall) methodology, or a newer methodology such as Agile. In Project Management, a project can only be managed using one methodology, and, in almost all cases, is not switched from one methodology to the other (usually methodology switching is not per project and is a decision made at the organization level), even when the other methodology is proven to be highly successful for that type of project. Being restricted by an exclusive, non-changeable methodology, either at the project level or the organizational level undermines and limits the potential of the project as well as the resources.

V. SYSTEM DEVELOPMENTLIFECYCLE

The growth of information system passes through various identifiable stages and these stages put together are referred to as the System Development Life Cycle (SDLC). This paper describes a process model for software project management that forms the basis of the system. This paper also describes a framework for inducing the sequence of operations that the project manager must perform: issuing instructions to workers in accordance with a plan based on the process model, progress evaluation based on progress reports sent from the workers, and analysis of the impacts of any problems detected. In order to provide these facilities, we analyze the actions triggered per unit of activity from the viewpoint of project management. Based on this analysis, this paper proposes a finite state machine model involving the actions and the states changed by the actions

Figure 3. Project Management Phases

 Requirement Definition

This is the first phase for every project this phase helps the industry person to understand the client and also help the client to understand the course, design, and platform requirements.

 Analysis & Design

Specialists from project management, software engineering, instructional design, and graphic design analyze the client's requirements, design software architecture. Based on the analysis, a design specification document is prepared.

 Development & Testing

First the prototype is created, which is functionally complete and runs on the actual platform envisaged or different prototyping techniques are used. Once the client approves the design and the prototype, the production team starts the development process. This is where scripting, creation of graphics, and coding take place. Testing begins right at the prototype phase and continues through various project milestones.

June - 2014, pp. 674-679

 Implementation, Deployment and Training

Once the system goes into production mode, comprehensive training is extended to the end-users; not only to administer and maintain it, but also to make them understand the underlying technology and development tools. The end-users are trained to use the application effectively.

 Documentation

Documentation soft copy and report is prepared at all the phases of SDLC.

VI. CONCLUSION

Service Oriented Architecture – Project Management Software dramatically improves the performance and the communication between your distributed and remote teams. Implementing Service oriented architecture in PMS distributes the load of a server by distributing the load on different machines thus making the application more robust thus supporting multiple users. SOA-PMS heighten the visibility and control of your application development lifecycle-giving you better control over the entire development process, from the management stage through development. The SOA-PMS allows you to move into the future without abandoning the past it provides interoperability that is fundamental to the application lifecycle. Globalization for many companies today, around-the-clock, nonstop design and development sounds too good to be true. . So how do you keep multiple teams-distributed around the campus or around the globe-working in concert and focused on the end goal? First, you need an integrated environment from managing change and configuration requirements and a system that is designed to give you visibility into the development process-one that will help you maintain control of the application lifecycle

ACKNOWLEDGEMENT

I would like to thank my guide for constantly helping and guiding me. His immense interest and knowledge in prototyping and applications has contributed a great deal in completion of this paper.

REFERENCES

[1] Arthur B. Pyster, Richard H. Thayer, “Software Engineering Project Management 20 years Later” IEEE

SOFTWARE Volume 22, Issue 5 (September 2005) Pages: 18 - 21.

[2] Abdullah SaeedBani Ali “A Study of Project Management System Acceptance” 0-7695-2268-8/05 IEEE

SOFTWARE, Proceedings of the 38th Annual Hawaii International Conference on System Sciences (HICSS'05) - Track 8 - Volume 08 IEEE 2005.

[3] Marc Frappier, Mario Richard “SMP: A Process-Driven Approach to Project Management” 0-7695-2056-1 IEEE

SOFTWARE Proceedings of the 37th Annual Hawaii International Conference on System Sciences (HICSS'04) - Track 8 - Volume 8 IEEE 2004 Page: 80253.3

[4] Pankaj Jalote, “Software Project Management in Practice”, Year – 2003, ISBN – 81-7808-664-6.

[5] JJ Jeng, Lianjun An “System Dynamics Modeling for SOA Project Management”, soca, pp.286-294 IEEE

International Conference on Service-Oriented Computing and Applications (SOCA '07), 2007.

[6] Liu Ying, FengChenhua, Zhao Wei, Su Hui, Liu Hehui, "A Case Study on Community-enabled SOA Application

Development," soca,pp.309-316, IEEE International Conference on Service-Oriented Computing and Applications (SOCA '07), 2007.