Skip to content
AL-705 · Skill Development Lab/Important Questions

Skill Development Lab (AL-705) - Important Questions

  1. Unit 514 Marks Low Priority

    For the given case study, explain the phases of the software product life cycle and indicate deliverables for each phase.

    Core evaluation of software development life cycle concepts applied to the unit 5 case study.

  2. Unit 514 Marks Low Priority

    Design UML diagrams (use-case, class and sequence) for the given case study. Draw each diagram and justify the major design choices you made.

    Standard UML modeling task frequently used to assess design ability from a case study.

  3. Unit 510 Marks Low Priority

    Discuss the importance of software development standards and describe how you would apply one standard (for example ISO/IEC 12207 or IEEE 829) to the project in the case study. Include expected benefits and key artifacts.

    Assess application of quality and process standards to a project scenario from Unit 5.

  4. Unit 510 Marks Low Priority

    For a specified scenario in the case study, select an appropriate design pattern (for example Factory, Singleton, Observer or Strategy), implement its structure (class diagram or pseudocode) and explain how it improves the design.

    Tests ability to map design patterns to practical scenarios in case studies.

  5. Unit 514 Marks Low Priority

    Perform effort estimation for the project described in the case study using the COCOMO basic or intermediate model. Show calculations, state assumptions, and prepare a tentative schedule with milestones.

    Covers effort estimation and schedule planning using a standard model.

  6. Unit 510 Marks Low Priority

    Prepare a detailed test plan for the case study project. Identify test types to be used, list test cases for critical modules (with inputs, expected outputs), and describe the test environment and entry/exit criteria.

    Focus on software testing planning and test-case design from case requirements.

  7. Unit 510 Marks Low Priority

    Create a Work Breakdown Structure (WBS) for the case study project, develop a Gantt chart showing task durations and dependencies, and propose resource allocation for each major task.

    Covers project management deliverables: WBS, scheduling and resource allocation.

  8. Unit 57 Marks Low Priority

    Identify potential risks for the project in the case study, classify them (e.g., technical, schedule, resource), perform a risk assessment matrix, and suggest mitigation and contingency plans.

    Assesses risk management and contingency planning for a given project scenario.

  9. Unit 57 Marks Low Priority

    Prepare a software configuration management (SCM) plan for the case study project. Include version control policy, branching/merging strategy, build and release process, and a sample change request workflow.

    Evaluates configuration management and build/release planning for a practical project.

  10. Unit 57 Marks Low Priority

    Describe a deployment and maintenance plan for the case study system. Include user acceptance testing approach, rollback strategy, training plan for users, and post-deployment support procedures.

    Addresses deployment, maintenance and acceptance processes for a delivered system.

Go to where you left off?

Quick Add to Notes

Save questions, your own notes and screenshots into notes filed by unit. It takes a free account.

Create free account

Have an account? Log in