zoilo

Bernal, Zoilo Enrico C.

9000085

Web Development 1

1. Describe the skills, functions, and job roles needed to develop a successful web project

• Project Manager
  • The web project manager coordinates and communicates the day-to-day tactical implementation of the web site project, acting within the constraints of the project charters and goals, project budget, development schedule, and quality objectives laid out in the planning stages. The project manager is the team member ultimately responsible for keeping the overall team activities focused on the site strategic objectives and agreed deliverables, and he or she continually monitors the scope of the project activities to ensure that the team stays “on time and on budget.” The project manager acts as the primary contact between the web team and the sponsor and manages the overall communication among creative, technical, and production elements of the web site team.
• Information Architect
  • The site information architect organizes and categorizes web site structure and content. The information architect is most active early in the design and planning phases of the project, developing content categorization schemes, consistent site terminology, content structure across the site, and site architecture diagrams that explain the overall site planning to both the sponsor and the web team members. Information architects also work closely with the site designers to craft page “wireframes,” the diagrammatic page grids that show how various areas of the page will be used to support site identity, navigation, and page content.
• Marketing Representative
  • The Marketing Representative is responsible for the distribution and advertising of the website that is being created or is created. They are also responsible for dealing with hosting websites and domain holding websites for the production of the website.
• Copy Writer & Editor
  • The Copy Writter & Editors role is to make sure that the website contains for copyright of other web related activities and they are also responsible for patenting the copyright of the content and things produced by the creators and editors of the website.
• Content Manager
  • The content managers role is to keep track of the content that is being shown and about to be shown on the website. They are also responsible for any content that is published to the public as to meet protocol and the standards of the company.
• Graphic Designer
  • The role of a Graphic Designer is to create visual templates that will be used as means for online communication and/or interaction. The skills involved in the production of such templates have grown in sophistication over time and now include disciplines as varied as Information Architecture, Interface Design, Information Design, Visual Design, etc.

• Database Administrator
  • The Database Administrator is responsible for the handling of accounts and databases of the websites. They are responsible for the distribution of accounts to the corresponding types and locations. They are also responsible for the accepting and declining of accounts that receive special access to the website.
• Network Administrator
  • Network Administrators role is to collaborate with the company's that are responsible for the hosting and network between the other things on the internet.
• Web Developer

2. Identify the common system development methodologies.

a. Waterfall Model

Waterfall is the oldest and most straightforward of the structured SDLC methodologies — finish one phase, then move on to the next. No going back. Each stage relies on information from the previous stage and has its own project plan. Waterfall is easy to understand and simple to manage. But early delays can throw off the entire project timeline. And since there is little room for revisions once a stage is completed, problems can’t be fixed until you get to the maintenance stage. This model doesn’t work well if flexibility is needed or if the project is long term and ongoing.

b. V-Shaped Model

Also known as the Verification and Validation model, the V-shaped mode grew out of Waterfall and is characterized by a corresponding testing phase for each development stage. Like Waterfall, each stage begins only after the previous one has ended. This model is useful when there are no unknown requirements, as it’s still difficult to go back and make changes.

c. Iterative Model

The Iterative model is repetition incarnate. Instead of starting with fully known requirements, you implement a set of software requirements, then test, evaluate and pinpoint further requirements. A new version of the software is produced with each phase, or iteration. Rinse and repeat until the complete system is ready.

One advantage over other SDLC methodologies: This model gives you a working version early in the process and makes it less expensive to implement changes. One disadvantage: Resources can quickly be eaten up by repeating the process again and again.

d. Spiral Model

One of the most flexible SDLC methodologies, the Spiral model takes a cue from the Iterative model and its repetition; the project passes through four phases over and over in a “spiral” until completed, allowing for multiple rounds of refinement. This model allows for the building of a highly customized product, and user feedback can be incorporated from early on in the project. But the risk you run is creating a never-ending spiral for a project that goes on and on.

e. Big Bang Model

A bit of an anomaly among SDLC methodologies, the Big Bang model follows no specific process, and very little time is spent on planning. The majority of resources are thrown toward development, and even the client may not have a solid grasp of the requirements. This is one of the SDLC methodologies typically used for small projects with only one or two software engineers.

Big Bang is not recommended for large or complex projects, as it’s a high-risk model; if the requirements are misunderstood in the beginning, you could get to the end and realize the project may have to be started all over again.

f. Agile Model

By breaking the product into cycles, the Agile model quickly delivers a working product and is considered a very realistic development approach. The model produces ongoing releases, each with small, incremental changes from the previous release. At each iteration, the product is tested.

This model emphasizes interaction, as the customers, developers and testers work together throughout the project. But since this model depends heavily on customer interaction, the project can head the wrong way if the customer is not clear on the direction he or she wants to go.

3. Find/List down the right free web hosting provider for your websites (blog & tutorial)

• SiteBuilder
• SiteBlog
• WebsiteBuilder
• Weebly
• Wix

4. Choose a domain name for your websites (blog & tutorial)

www.whatslifewithoutwhimsy.com

send to giesellev25@yahoo.com

familyname_finals