Evaluating Your Tools and Methods

8/2/2019 Evaluating Your Tools and Methods

1/28

Evaluating Your Tools and

Methods


2/28

Contents

1. Overview

2. Data backup

3. Document availability4. Source control versioning

5. Software builds

6. Bug tracking7. Release method


3/28

1. Overview

Waterfall Process

Spiral Process

Tools and Methods on Process Q&A for SGTs Projects


4/28


5/28


6/28


7/28

Q&A for SGTs Projects


8/28

2. Data backup

Solution overview

Full Backup method

Incremental Backup method Differential Backup method

Methods & Tools

What we have to do


9/28

Solution overview


10/28

Full Backup method

Backup frequency = ?

Backup tools = ? Evaluation = ?


11/28

Differential Backup method


Backup tools = ?

Evaluation = ?


12/28

Incremental Backup method


Backup tools = ? Evaluation = ?


13/28

Methods & Tools

Backup Frequency

Disk-Only and Tape Backup

Offsite Backup


14/28

Backup Frequency


15/28

Disk-Only and Tape Backup

Corrupt source files might corrupt the backup copy andpermanent records do not exist.

A disgruntled employee can alter the data. The backupfiles will store a copy of the problem code as theadministrator creates these periodically but does notcreate a permanent record.

Occasionally, hardware does fail. Although unlikely, bothdisks could fail, obliterating all your files.

Users can delete files by accident. If you discover a lostfile after the administrator makes the backup image, youcannot recover the file.

Disk-to-disk backups are usually done with onsite disks.Consequently, if disaster strikes your building, you willhave lost everything.


16/28

Offsite Backup

Evaluation: ?


17/28

What have we to do


18/28

Document availability

Overview

Software Developments Documents

Plone tool


19/28

Overview

Documents are product of process

No Process No Document


20/28

Document kinds for SoftwareDevelopment

Product definition documents and specifications Technical background information Internal design documentation

Customer system architecture Data file format information Database design schemas Process definitions

Application programming interface (API)description Schedules


21/28

Plone Tool

Allow easy searches for files

Allow different levels of access for differentaccount groups

Make file uploads simple for all file types

Make reading documentation easy,

requiring a single click to open andinstantly view documents


22/28

Source Control Versioning (SCV)

Define

SCV Progress

Tree Method Important note


23/28

Definition

Source control versioning (SCV) allowsyou to save and retrieve multiple versionsof different files, tag groups of files, and

retrieve desired versions of files in astraightforward way


24/28

SCV Progress


25/28

Important note

None conflict

None corrupt

Clear numbering Clear Tracking


26/28

Tree Method

Root Left Right

Left node: new Features

Right node: change/modify/fix bugs


27/28

Software Build Method and Timing

A software build methodis the approachyou use for extracting the desired versionsof source files

The build process for each product iswritten downand tested successfully by asecond engineer

Evaluation Daily buildsand nightly builds


28/28

Bug tracking

Overview