Sheraz Salim Registration Number 20388626

This Report is on Banking online software For Module No CO4805 Module Name; Project Managment Module Tutor; Amanda Jane Gregory Report Submitted by Sheraz Salim REG 20388626

Module No. CO4805 Module Name: Project Managment

Sheraz Salim Registration Number 20388626

Project Management Online Banking Introduction and project scope

The scope of this project is to design online banking software. The software must meet the client requirements, and providing all the essential information. The software function is to provide online statements, transfer fund from one account to any account, setting direct debit, utilities bills, and bill manager. This is all based on integration of E-commerce. A bank will send a customer unique internet banking ID. Once internet banking ID will be type by customer the software will ask few questions, the customer provided them, at time of opening bank account. On the base of this information s/he will be qualified to access onto the online banking software. However, there are hazards of malicious and vulnerability activities. To provide the security of online banking, if existing account holder answer incorrect the secret question three times, the software will block the ID and s/he should be advice to contact the bank.

Job Specification
A job specification for all members of staff is necessary if there is to be clarity about what they are responsible for and to whom they are responsible. Furthermore, they need to know to whom and how to refer when they reach the boundaries of their own decision making role. [1] Due to nature of the any project, different people are required to develop a project, and in this project everyone perform its role. In our project we have four managers. Project manager Business Manager Development Manager Testing and Quality Manager Every manager has his own team. In each team, there is a team leader to look after the project and giving report to their manager every day going task. A strong team is the nucleus of and can ensure the success of project. The team members are asked to deal with specified constraints of time and money. Some time under great stress. As project mangers, you should need to give technical guidance, management expertise to your team leader, plus a significant intangible, support and enthusiasm. [2]

Module No. CO4805 Module Name: Project Managment

Sheraz Salim Registration Number 20388626

Life Cycle
As developing the banking software, we must have to use the guideline of any life Cycle. Life cycle is a backbone of any project to fulfill its requriemnt. The life cycle consist of four to six phases, for a six phase model, the phases are concept, definition, design, development or construction, application, and post completion. For a four phase model, the phases are concept, planning, execution, and close out. [3] Choosing a life cycle is an increasing trend of last three decade. There are many factors to choosing it and some are as given below. Choosing the most beneficial procurement strategy, Determining cost drives, Providing objective for program control, Assessing new technology application Forecasting future budget needs. [4] Most popular and widely use life cycle are Water fall life Model Prototyping Model Exploratory Prototyping Spiral Model Code and fix etc.

Prototying for using for client

As there are many different kinds of life cycle to choose. After having a fruitful meeting with our managers, we reach a conclusion to adopt prototyping method. Compare to other life cycle model we find prototyping much more to offer compare to other one. Likewise during the requirements specification the developer can show the client a optional working system at near the beginning stage. The consumer is not always sure what they want to system to do. It is very hard for consumer to understand properly and be able to state detailed well-designed needs, unambiguously before they have an opportunity to experiment interactively with the option. A prototyping give a much clear picture and better understanding to fulfil the requirement of software cycle. [5]

Why Prototyping Used

It is an effective tool for showing how a design meet the client requirments frequently not completely implicit in the early development stages. When we reach on to the design, its understandable how everything is working together, and discover the need of any adjustment require. In information systems engineering prototypes are used to identity and validate requirments, to verify design and provide a base line for the development of system. [6]

Type of Phototyping
Throwaway Functiional / Evolutionary 3

Module No. CO4805 Module Name: Project Managment

Sheraz Salim Registration Number 20388626 Cosmetic research

Advantages of Phototyping
Reduce development time and cost Developers receive experimental consumer updates User involvement requires Consumer satisfaction higher in results Consumer requirements easier to determine Faster development Quick production of some thing to consumers [7]

DIAGRAM OF PROTOTYPE LIFE CYCLE

Disadvantages of Phototyping
Major amount of end user dedication and may then result in a less efficient use of system funds The continuous modification of the system specification result in excess time delay and the development of an incomplete system, an inadequately document system. Accounting information systems development : managine change, chapter 16, page 877 show the way to lacking analysis Developers can become too much attached to their prototypes [8]

Life cycle choice of devloping software

Module No. CO4805 Module Name: Project Managment 4

Sheraz Salim Registration Number 20388626 We as a project team working on a banking online software development for bank which will be introducing many features for the clinet customers and it will be use ful for us to make a good repuation in the market. In response we shall get more contracts and make our value. When it is given to the end user by our customer it shall be need to accept by the custoemr first. Due to our coustmer and the role perfomance of this project our group project has chosen water-fall-prototyping life cycle modle. The non-operational type of prototyping life cycle will give us the simplicity of make a prototyping of the project so if the customer would like to give us any feedback and want to change any phase if they needs. It can be used as a communcation tool between the analyst and the end user. If the customer conclude the prototype design for the project then dvelopment team start working on it. [9] .

Waterfall-Prototyping SDLC model

www.synlog.net/images/Waterfall-2.jpg

The prototyping lifecycle is follow by Waterfall lifecycle in this regard we find out what customer actually need are.

Advantages
There are following advantages of Prototyping-Waterfall Lifecycle; Developing Prototype helps in taking clients feedback that helps in giving satisfaction to our client. It can be easy to schedule. Once the prototype is agreed by the client, we can go on continuing with waterfall model. In this type of model, the chances of changing the requirements after completion of the project are very less. It saves a lot of time for coding and designing as the prototype is been approved by the client. Testing and quality assurance time is saved.

Module No. CO4805 Module Name: Project Managment

Sheraz Salim Registration Number 20388626

Disadvantages
Following are the disadvantages regarding the lifecycle; As the project pass through two stages, it is somewhat time consuming as compared to others. When the prototype is finalised and waterfall is being worked on; the technology cannot be changed during the project.

Alternative life cycle

The alternative life cycle to choose for this project could be V- Model. As it offers promote planning and desigining in anticipation of testing. The V- Model highlight planning for verification of software system in the early stage of project, it also encourages confirmation of all deliverables not just the sytem. Moreover it is easy to use it. [10] The other option to use a life cycle is Spiral model; this is often referred as the spiral lifecycle. This is combination of both the waterfall and prototyping lifecycles. The advantage of this model is flexible as compared to waterfall method or the prototyping method. In some cases it is easy for cost calculation and even the time management.

Project Plan
A project is exclusive effort to introduce or produce new product or service meeting the requirements to certain condition and applicable standards. This effort is completed within the project parameters including fixed time, cost, human resources, and asset limits. [11]. We divid the project in different tasks, developing desgin, quality maintains and assurance, software tester and business analysis. Each team has a member of 10 to 20 personos. Task 1: Analysis The bottom line is to develop software on online banking depending on the raw data we get from the search that we have conducted. Choosing a software development, we analysis and start thinking and searching for the other website similar to online banking facility. After spending some time our group project reach a result that we should make a software reliable and more efficient in job search. This is how we primarily get our case study done. Task 2: Planning In planning the group of manager have to decide how to handle the project, and how to keep the daily work work uptodate. Likewise getting update from each individual manger to keep the log of project plan. Task 3: Recruiting There are various roles involved in project to do so we assigned various tasks that we need to develop the project and to divide amoung our project groups. Furthermore Human resource manager is responsible for company management, personal management and administration. Module No. CO4805 Module Name: Project Managment 6

Sheraz Salim Registration Number 20388626 Task 4; Phrototyping Phototyping is the life cylce to understand client need. Later we use waterfall method for making the software development process. Task 3: Designing Making software requirments specification (SRS) and planning their functionalities and modules have been created. Making rough calculation on the expenses and resource which used on to the project. keep dairy of requriemts we moved one step each ahead and doing alignment in the software with particular to SRS. Task 4: Development The development process requires coding and the implementation on the back end of the website. The task was related to the developer who generate code for every set of attributes. During this task we are providing all the necessary information to team. As developing banking software need more security to customer end to making it save. Task 5: Testing Testing part paly an huge role, a testing team is responsible for any gap or any error during the development of the banking software and finding the alternative and providing feedback to developmlent departement. Task 6: Maintenance This team monitor the project thoughtout its life cycle. The team monitor the project at every single stage and making sure that right resource are allocated at right time. Business analyst is on of the most fast growing role in infromation techonlogy. They can be found in major companies and are important member of any IT team, wheater in the private or public sector. Business analyst provides a clear, step by step guide to how the business analyst can perform a role. [12]

Functional requirment
The functional requirments defines a function of banking software stystem. A software that state a function that software constituent must be capable of performing it. Its the stage where business analyst define to it IT team how to define the rules, and what customer need are. It there are any similar software to it to analyse it and offering a new feature. Additionally some time functional requimrent may be technical detail, like business analyst made the rule define by client to fulfill their requirment.

User Requirment
A user requirment is essential part of handing project as what are the client need and how to define and implenmet it. User Requimrent also depends on the market like what client customer except from it.

Non Functional
Non functioanal requriemet in software system engineering, a software requirment that describes not what the software will do, but how the software will do it. For example software performance requrients, software external interface requriemnt. However they are diffecult to test, usually evaluated subjectively. [13]

Deadline
The time is given to each group or task from 1 month to 2 month depends on what task they doing. Each task is important for the project. if project is taking more time to Module No. CO4805 Module Name: Project Managment 7

Sheraz Salim Registration Number 20388626 collect data or submit it to the developing team need all the requriemnt of daily basise task. We should keep these guidelines to maintain the project How and at what stage to re-plan How to look after the control project Determine the accurateness is reached Administration the infromation needed What are the date of delivery of software to client

Estimating duration of task of project

If the time management is not given or runout or not available, then a simple mathematical model can be used as a supply to calculate the duration of time required for any movement. Therefore We have implemented the same model to have the duration of the movement. While three time estimates are required to calculate time for an activity they are: t0 = the shortest or most optimistic duration tm = the most likely duration. tp = the longest or the pessimistic duration te = the calculated estimate of time The calculation of time is t0+4 tm+ tp 6 In some cases it is considered as the over-optimistic one so the formula can be framed as follows: te= t0+3 tm+2 tp 6 te=

In most cases it is not possible to estimate an exact time requirement for an activity hence, small errors will occur and small planning adjustments are made. [14] Project Management An international Perspective, by Ralph Keeling MACMILLAN BUSSINESS Page 154& 155

Team work
Our team consists of four members sucessfully complete this project, Team work is one of the crucial and most important parts to the plan. Having a meeting in library and keep in touch through different channel like email, phone calls and netmetting in a good atmosphere help us a lot to understand the requirement of the project. Usefull Module No. CO4805 Module Name: Project Managment 8

Sheraz Salim Registration Number 20388626 communications betwee the team of members are essetntial for indiviual development and for the development of company as well.After having few on and off long meeting we finally undersatnd how to manage and take each step futher toward building a project in a smooth way. Our team worked together in collecting infromation for develpoment of banking software. Many other different sources were very usefull like websites, books and some online journals publishd on technologies regarding to software development. The project work was divide amoung us accordingly as fallowing. Planning and staffing Organising Leading Monitoring Implementation Perfomance Planning meeting are perfored when any action needs to be taken in respect of project. in these meeting any individuals can speak on sometihng that will be beneficail to the project, like what meaurement should be taken and how to handing the project in different in effective way to helping all. The realationship between our team members are excellent in result we achieved our goals and task on time. However we faced some diffeculties but we easly manage them on time.

Module No. CO4805 Module Name: Project Managment

Sheraz Salim Registration Number 20388626

Module No. CO4805 Module Name: Project Managment

10

Sheraz Salim Registration Number 20388626

Reference
[1] [2] [3] [4] [5] Teacher Appraisal, Doreen Poster, page no 40. Project Management, Joan Knutson, chapter 3, page 20 The project managers desk reference, James P. Lewis, page no 13 Life Cycle Costing, B. S. Dhillon, chapter 3, page 30 Software Engineering for Student, Doug Bell, chapter 23, page no 310.

[6] University of Glamorgan, web address ; http://www.comp.glam.ac.uk/pages/staff/tdhutchings/chapter8/sld009.htm [7] Accounting information systems development: managine change, chapter 16, page 877 [8] Accounting information systems development : managine change, chapter 16, page 877 [9] Sacramento state University Web address:http://www.csus.edu/indiv/m/martinm/116-prototype/sld003.htm [10] Computer Systems Validatin, Guy Wingate, chapter 5, page 103 [11] Project Management, Joan Knutson, Ira Bitz, chapter 1, page 1 [12] UML for the IT Business Analyst: A ractical Guide to Object-oriented Requirments Gathering, Howard Podeswa, page no 378 [13] Non Functional Requirments in Software Engineering, Lawrence Chung, Brain A. Nixon, Eric Yu, John Mylopoulos, chapter 1, page no 6. [14] Project Management An international Perspective, by Ralph Keeling MACMILLAN BUSSINESS Page 154& 155

Module No. CO4805 Module Name: Project Managment

11

Sheraz Salim Registration Number 20388626

Module No. CO4805 Module Name: Project Managment

12