Dear Sirs,
I'm a Senior IT Risk Consultant with prominent achievements in IT Risk Management in commercial banking.
Skills:
Good business and technical acumen;
Strong ability to translate business system requirements into clear and
unambiguous specifications (functional and non-functional);
Strong orientation to deadlines and results;
------
Master of Science degree in IT, Project Management major from USA University - dissertation topic: IT Risk Management in SW Development in Retail Banking;
Note: Willing to send resume,if necessary - please do provide e-mail address.
Please find below a section of an interim report of the dissertation I've completed for my Masters degree.
3 SOFTWARE LIFE-CYCLES AND DEVELOPMENT METHODOLOGIES
This chapter emphasizes the necessity of having a corporate Software Life-Cycle/Development Methodology ready for use. This enables a structured development of an Information System into phases, facilitating Risk identification at a phase level, right from the Inception phase. The identification of Risks will somewhat be eased by breaking down each of the project phases, down to its lowest level into a set of related activities/tasks/sub-tasks.
3.1 SOFTWARE LIFE-CYCLES
3.1.1 The Waterfall Model
This briefly describes the main construct of the model and its main set of features.
3.1.2 The Prototype Model
This briefly states the basic reason for prototyping, and the characteristics of the various types of prototypes.
3.1.3 The Choice of the Approach(es) and the Need to have one
This describes the rationale for the choice of one or the two approaches (an hybrid solution is feasible at occasions, depending upon the nature of the system components), as opposed to RAD, spiral, and Incremental Life-Cycles which are out of the Retail-Banking context in xxxxx, hence unused. The importance of having a corporate approach readily available is justified as a requisite for early Risk Identification, at phase level, by splitting the development process into phases.
3.2 SOFTWARE DEVELOPMENT METHODOLOGIES
3.2.1 Overview
This sub-section addresses the Design process using a Software Development Methodology and its relevance in order to have development of Information Systems within controlled environments.
3.2.2 SASD
This sub-section briefly addresses the main construct behind SASD. No insight is necessary, for the ultimate objective of the research does not call for more than just a brief reference.
3.2.3 STRADIS
This sub-section briefly addresses the main construct behind STRADIS. The ultimate objective of the research does not call for a comprehensive reference.
3.2.4 The Choice of the Approach
This sub-section addresses the rationale behind the choice of one of the approaches.
The choice is made based on parameters like, Costs (A Cause and Effect Diagram is drawn), Benefits (a Cause and Effect Diagram is also drawn) and Organisational Maturity (an Organisation Maturity Model is produced).