Sunday, February 24, 2008
Suggested MCQ answer for DMID
Below is the suggested mcq answer provided by Gemira for DMID.
Visit here
Posted by Zack at 9:23 PM
Thursday, February 21, 2008
DMID Summary Notes
Below is my COMPLETE Summary Notes for DMID. ENJOY! LOL
Click Here To Download
Posted by Zack at 7:03 PM
Tuesday, February 19, 2008
Suggested MCQ Answers for OS year 05,06,07
Below is the link to my suggested mcq answers for OS.
Enjoy!
Click here to go!
Posted by Zack at 8:04 PM
Saturday, February 16, 2008
SWENG Summary Notes
This is my Summary notes for SWENG. Download at the link below.
Download Here
Posted by Zack at 3:28 PM
OS Summary Notes
This is my Summary notes for OS. Download at the link below.
Download Here
Posted by Zack at 3:26 PM
Wednesday, February 13, 2008
Guide to Software Engineering Part 4
Capability Maturity Model Integration (CMMI) is the best practices that address the development and maintenance of products and services covering the product life cycle from conception through delivery and maintenance. It is a suite of best practice guidelines to help an organization improve its software life cycle processes.
Note: The Quality of a system or product is highly influenced by the quality of the process used to develop and maintain it.
Process Areas (PAs) are a collection of best practice guidelines for improving a particular area in software engineering.Four main categories:
- Process Management
- Project Management
- Engineering
- Support
Measuring process- Capability Level (CL) ~ Continuous Representation
o Measures how well an organization has performed the best practices prescribed in a single process area.
- Maturity Level (ML) ~ Staged Representation
o Measures how well an organization has performed the best practices prescribed in a group of process areas.
Five Maturity Level- Level 5 (Optimizing)
- Level 4 (Quantitatively Manage)
- Level 3 (Defined)
- Level 2 (Managed)
- Level 1 (Initial)
Posted by Zack at 7:57 PM
Guide to Software Engineering Part 3
Peer Review is a systematic and formal process of analyzing and examining software life-cycle work products to identify and remove defects. The purpose is to remove defects from work products early and efficiently and is performed by peers with similar authority and responsibility.
Peer Review Process in Phases
Entry Criteria -> Kickoff -> Check -> Inspection Meeting -> Correction -> Exit Criteria -> Complete
Types of Peer Review
- Buddy Checks
- Circulation Reviews
- Technical Reviews
- Walkthroughs
- Inspection Reviews
Roles and Responsibilities
- Moderator
- Author
- Reviewer
- Recorder
Five Supporting Documents for the Formal Inspection
- Review Initiation Form (RIF)
- Individual Inspection Form (IIF)
- Consolidated Inspection Form (CIF)
- Inspection Feedback Form (IFF)
- Inspection Summary Form (ISF)
Posted by Zack at 7:55 PM
Monday, February 11, 2008
Guide to Software Engineering Part 2
Software Configuration Management (SCM) is the discipline of identifying, organizing, and controlling changes to the software to maintain the integrity of its configuration.
The Need to Manage Change
- Overwriting
- Bug fixes
To perform SCM, you need:- A nomenclature(naming) to identify work products in the process
o Baseline
o Configuration Item
- Processes
o CM policies and procedures (CM Plan)
o Change request process
o Version control and naming
o CM audit and status accounting
- Roles and responsibilities
o Configuration Manger
o Change Control Board
o Auditor
- Tools
o Configuration Repository
o Version Control
Configuration Item (CI) is a work product that is place under configuration control (Baseline).E.g. Minutes of Meeting, requirement specification project proposal, codes, test plan, user documentation.
Baseline is a specification or product that has been formally reviewed and approved which can only be changed through forma approvals.
Roles and Responsibilities- Configuration Manager
- Change Control Board (CCB)
- Software Engineers
- Project Manager
Configuration Audit is the activity performed independently to evaluate the conformance of CM policies and procedures.
Status Accounting is the recording, monitoring and reporting of configuration management information and the purpose of it is to maintain continuous record of changes and actions for all baseline CIs.
Posted by Zack at 7:14 PM