Skip to main content

2 posts tagged with "Development"

View All Tags

· One min read
John M Telford
info

The Iterative Website Development Stack illustrates how websites are developed and deployed to the Internet. It is web browser agnostic. What works for big screens, works for small screens.

Developer Iterative Development Stack

Development Stack


caution

The key Iterative Development technologies are git and GitHub.

  • Team members use the Website Development Stack to develop and deploy websites to the Internet.

    • There would be confusion and possible defects created if Team members were to directly make changes to the same project repository.

    • A solution to this problem is to have one central repository controlled by a gatekeeper. Each team member forks a copy to their GetHub account and makes a clone of it on their workstation.


  • Each developer makes changes to their repository clone. They cannot directly make changes to the central repository.

    • Team members commit changes to their local repository clone

    • They may deploy their local repository to a private Internet website for stakeholders to see and give feedback. See Preview Deployments

  • The process is managed using GitHub for Teams. When stakeholders determine developers changes, defect fixes, or new features are ready, a GitHub pull request is made by developers to the central project repository.

    • Project team members and the gatekeeper are notified by GitHub of the pull request. They may examine, comment on, suggest possible changes, and test the code.

    • When the team agrees on developers changes, they are committed to the central project repository by the gatekeeper. This process is repeated for each developer set of changes.

    • Iterations of the central project repository may be deployed by the gatekeeper to a private website for stakeholders viewing. See Preview Deployments

  • The next step is each developer pulls the central repository changes and commits them to their local repository copy of the central project. This process keeps team members up to date on changes.

  • The central project repository may be deployed to the public Internet by the gatekeeper after stakeholders agree there have been sufficient development and testing iterations.

—-

· 2 min read
John M Telford

The basic idea of Iterative Development is to develop a system through repeated cycles (iterative) and in smaller portions at a time (incremental), allowing iterative development teams to take advantage of what was learned during development of earlier parts or versions of the system.

Teams

Teams

Iterative Development Teams

ItIterative website development teams working together can help optimizing website costs and lower some the difficulties creating websites

Iterative website development enables the Define, Design, Develop, Deploy and Maintain teams to be operational at the same time creating, testing and remediating website defects

Central Repository

The core of Iterative Development is a file central repository controlled by a gatekeeper.

GitHub is a Distributed Version Control Systems enabling multiple teams to work separately without having an impact on the work of others. GitHub is a central online web hosted project repository for all project files. It is a unified source of truth. It helps teams collaborate and maintain the entire history of project file changes. Teams can view history of all changes and go back to previous file versions.

It helps answer the questions who changed what, where, when, and why?

All team members have their own local copy of the central project repository. They make changes, fix defects, add new features to their repository, without interfering with others team members, or the central repository.

Team members cannot directly make changes to the central repository. They may deploy their copy of the repository with their changes, to a private Internet website for stakeholders to see and give feedback.

When stakeholders determine some changes, defect fixes, or new features are ready, they will be committed to central project repository, and team members update their local copy by pulling central repository changes into their local repository. This process keeps team members up to date.