An introduction to environment management

A short introduction to environment management. What is it and
what relationship does it have to business intelligence ? How
can it aid development and help keep costs and time scales to a
minimum ?

Transcript

1. Environment Management • Software development environment management – Test environment management • Release management • Change control • Access control • Benefits • Problems www.semtech-solutions.co.nz info@semtech-solutions.co.nz
2. Environment Management – What is it ? • Control of software development environments – Control access – Control change – Ensure that they are fit for purpose – Ensure systems and software • Reflect current release • Reflect stage in development • Reflect current use i.e. dev / test www.semtech-solutions.co.nz info@semtech-solutions.co.nz
3. Release Management • Control change by using – A backed up software repository – A dedicated change manager – A change control process and tool – Access management to • Tools • Environments • Code Repository • Data www.semtech-solutions.co.nz info@semtech-solutions.co.nz
4. Change Control • A change control process • Problem reporting via a tool • Vetting of problems reports • Change requests linked to problem reports • Change requests used in testing • Change requests incorporated into releases www.semtech-solutions.co.nz info@semtech-solutions.co.nz
5. Access Control • Control access by project staff to – Environments – Data – Tools • Control access by role – dev, test, release, analyst, project manager • Avoid undesireable and expensive changes • Shorten delivery times by avoiding mistakes / confusion • Partition env usage and manage need www.semtech-solutions.co.nz info@semtech-solutions.co.nz
6. Benefits • Reduced cost due to undesirable env changes • Environments better reflect – State of system, stage, architecture • Better management of time scales • Benefits for staff morale and ownership www.semtech-solutions.co.nz info@semtech-solutions.co.nz
7. Problems • Project pressures – Need to use test for development – Adhoc access / change – Not advisable – plan for project needs – Police usage to ensure costs / time scales • Desire to “cut corners” – Adds to costs and increases time scales • Complacency – Use process to ensure best practice www.semtech-solutions.co.nz info@semtech-solutions.co.nz
8. Environment Management www.semtech-solutions.co.nz info@semtech-solutions.co.nz
9. Diagram Details • Environment volume decreases by stage – i.e. Need more dev envs than uat • Processes and environments use code repository • Dev environments can be cut down versions i.e. – May not contain all system components – Reduced volume of data • Controlled release to environments • Backup strategies to avoid loss www.semtech-solutions.co.nz info@semtech-solutions.co.nz
10. Contact Us • Feel free to contact us at – www.semtech-solutions.co.nz – info@semtech-solutions.co.nz • We offer IT project consultancy • We are happy to hear about your problems • You can just pay for those hours that you need • To solve your problems