WEB PROJECT PHASES

Get Complete Project Material File(s) Now! »

Project Management & Technology Development

Management Methodologies “A project methodology is the entire structure used to support a project. It consists of templates and processes and is the generic standard for all projects used in a company. A development methodology is specific to the technology and is more technical in nature.” [9] As mentioned before in section 2.2, there are some functions or factors that should be taken into consideration when managing a project. Charvat in his book [8] makes a very helpful comparison between different methodologies based on those factors plus the project size factor, see Table 1. This comparison is still relevant, but many of those methodologies are not developed or even changed after first time in use, or some of them are not used any more. On the other hand, this comparison suggests to the author metrics to use in development the Z‐Methodology and how it should be developed; especially that it is mixed of these two types of methodologies, (Project Management Frameworks Methodologies & Technology Development Management Methodologies) and specialized for web projects.

Methodology Structures

A methodology by definition by Charvat is “Methodology is a set of guidelines or principles that can be tailored and applied to a specific situation. In a project environment, it can be a list of things to do. This could be a specific approach, templates, forms, and even checklists used over the project life cycle.”[9] Through the project life cycle, many clarifying activities or tasks must be done to arrive to the end point. To manage such activities, a list of guidelines should be followed, and a set of forms should be filled. These activities, guidelines and forms are defined as a methodology in a project environment. Acc ding to Murc or h[3], most methodologies have four different components: 1. Guidelines: In order to get a successful application development, necessary specific steps should be followed, these steps are the Guidelines, and they contain advices and recommendations of how to control the development process. 2. Techniques: The detailed process descriptions that support the activities throughout the entire software development life cycle (SDLC). Techniques provide assistance for completing the deliveries. 3. Tools: The methodology which depends on past project experiences is consolidated with the project management tools. Most methodologies do not necessarily follow of the primary application development software, they are mostly independent. This means that this software can be used with any language, from legacy COBOL systems that are 30 years old to fourth‐generation languages (4GLs), CASE tools, to Object‐Oriented systems. 4. Templates: Reusable documents, checklists, and forms that give the user assistance and advice.

Why Use a Methodology?

For the application development process, using a standard approach or a methodology creates major benefits and significant productivity gains. Project management benefits include the following: • Both management and users know in advance what they can expect from each project. Predefined sign‐off points, which are sometimes called Milestones, provide management and users with the ability to give their approval and to ensure that the project’s goals are met. • Results are of high quality .Verification and quality requirements and are integral parts of any good methodology. Quality assurance reviews or audits give management an independent assessment of the caliber of work done. • Surprises or any unexpected events, such as cost overruns, scope changes, late implementation and other risks, can be minimized. Methodologies have risk assessment and control procedures to mitigate project risk. • Increasing the productivity .To make the Operation, a group of guidelines must be followed, there is no “figuring it out or making it up as you go”. • A methodology gives standards that everyone can follow, which means improving the communication between the audiences. [9 Ibid, p140‐142]

Developing & Design Z-Methodology

As mentioned before in section 3, the Meta‐methodology is used to developing Z‐ Me o th dology. 1. State the purpose of the proposed methodology To identify the problem in hand, the author read different literature in field, related to software, websites, and project management, and come up with the following propose: Proposed methodology is built to solve the main problems or aspects not covered in software development methodologies. As mentioned before in section 2.9, the differences between software and website are a reason to develop new methodology for manages a website project. Furthermore, as mentioned before in section 2.4, the differences between project management and development management methodologies give an idea to develop a new methodology handle sides, business and technical aspects.

Contents :

• 1 INTRODUCTION
  • 1.1 BACKGRO NU D
  • 1.2 PURPOSE / OBJECTIVES
  • 1.3 TARGET AUDIENCES
  • 1.4 DELIMITATIONS
  • 1.5 THESIS OUTLINE
• 2 L E IT RATURE REVIEW
  • 2.1 HANDBOOK
  • 2.2 PROJECT & WEB PROJECT
  • 2.3 WEB PROJECT PHASES
  • 2.4 PROJECT MANAG MENT E & TECHNOLOGY DEVELOPMENT MANAGEMENT METHODOLOGIES
  • 2.5 METHODOLOGY STRUCTURES
  • 2.6 W U HY SE A METHODOLOGY?
  • 2.7 META‐METHODOLOGY
  • 2.8 SOFTWARE ENGINEERING
  • 2.9 WEB ENGINEERING
  • 2.10 RUP
  • 2.11 PRINCE
  • 2.12 WATERFALL
  • 2.13 UNICYCLE
• 3 METHODS
• 4 ANALYSIS & DESIGN
  • 4.1 DEVEL PING O SIGN & DE Z‐METHODOLOGY
  • 4.2 DATA COLLECTION
  • 4.3 ANALYSIS OF LITERATURE
• 5 RESULTS
  • 5.1 Z‐METHODOLOGY
• 6 CONCLUSION AND DISCUSSION
• 7 REFERENCES
• 8 APPENDICES

GET THE COMPLETE PROJECT
WEB PROJECTS MANAGEMENT BETWEEN THEORY & PRACTICAL APPLICATION