[go: up one dir, main page]

0% found this document useful (0 votes)
638 views7 pages

Unit 30 Application Development SOW FGW Vietth

This document outlines a scheme of work for a unit on application development. It includes 4 learning outcomes related to producing software design documents, using design methodologies and tools, working individually and in teams, and evaluating applications. The unit consists of 40 sessions covering topics such as requirements, user interface design, object-oriented analysis and design, ASP.NET MVC, authentication, and presentations. Sessions include theories, activities, and practices like modeling, design assignments, and workshops to help students achieve the learning outcomes.

Uploaded by

Hoang Duc Quang
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
638 views7 pages

Unit 30 Application Development SOW FGW Vietth

This document outlines a scheme of work for a unit on application development. It includes 4 learning outcomes related to producing software design documents, using design methodologies and tools, working individually and in teams, and evaluating applications. The unit consists of 40 sessions covering topics such as requirements, user interface design, object-oriented analysis and design, ASP.NET MVC, authentication, and presentations. Sessions include theories, activities, and practices like modeling, design assignments, and workshops to help students achieve the learning outcomes.

Uploaded by

Hoang Duc Quang
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 7

SCHEME OF WORK

UNIT 30: APPLICATION DEVELOPMENT


Learning outcomes (BTEC, globalization):
 LO1: Produce a Software Design Document by analyzing a business-related
problem and deduce an appropriate solution including a set of initial
requirements.
 LO2: Use design and development methodologies with tools and techniques
associated with the creation of a business application.
 LO3: Work individually and as part of a team to plan and produce a
functional business application with support documentation.
 LO4: Evaluate the performance of a business application against its
Software Design Document and initial requirements.
Objectives (FGW, localization):
 Use modeling tools such as use case diagram, screen flow diagram,
requirement process to capture and analyze solution requirements.
 Use object oriented models and tools to design the solution.
 Explain different design and development methodologies and tools.
 Implement a secured web-based application with MVC approach.
 Critically evaluate a business application.
 Produce user guide and technical document.
F2G Syllabus:

Learning
Sessions Session Activities
Outcome(s)
Theory:
 Introduction to the unit content and unit assessment.
LO1  Requirement concepts and requirement modeling
 Modeling tools
Session 1,2 Topic: Software
Requirement Practice:
Concepts
 Investigate real-world scenario to identify problem
requirements
 Draw use case diagram for the requirements

1
Learning
Sessions Session Activities
Outcome(s)
Theory:
LO1  Screen flow diagram.
 Interaction Flow Modeling Language (IFML)
Session 3,4 Topic: User
Interface Design Activity:
 Answer user interface design problems
Theory:
LO1  Requirement process
Topic: Requirement  Requirement clarifying
Session 5,6  Common practices, problems
Process
Practice:
 Create Q&A sheet to clarify requirement.
Theory:
 General Introduction to OOAD
LO1, LO2  Object modeling technique
 Three models
Session 7,8 Topic: Object
Oriented Analysis  Four phases
and Design
Practice:
 Draw class and sequence diagrams
Theory:
LO1, L02  Explain assignment requirements
 Instruct to do the assignment
Session 9,10 Introduction to
Assignment 1 Practice:
 Carry on assignment: analyse application requirements
Theory:
LO2  UML concepts
 Simple analysis/design UML diagrams
Session 11,12 Topic: Unified
Modeling Language
(UML) Practice:
 Carry on assignment 1: design application functions
Theory:
LO2  Software design principles
 Simple design pattern in the common situations
Session 13,14 Topic: Object
Oriented Design in
Practice Practice:
 Carry on assignment 1: design application functions

2
Learning
Sessions Session Activities
Outcome(s)
Theory:
 Design process
LO2  Design workflow
Session 15,16 Topic: Design  Design document
Process
Practice:
 Review of student progress on the unit assignment
Practice:
LO1, LO2  Application development workshop with tutor support to
Session 17,18 Topic: Workshop introduce different design and development methodologies.
 Discuss, select or synthesize a design and development
on Assignment 1
methodology for use with the creation of your application

Theory:

 MVC patterns
LO3
 Introduction to ASP. NET MVC Framework
Session 19,20 Topic: Introduction  Razor Engine
to ASP .NET MVC
Practice:

 Review and submit assignment 1


Theory:
 ASP.NET MVC project
 Controller
LO3
 URL Routing
Session 21,22 Topic: Creating  View
APS.NET MVC  Model
application
Practice:

 Create sample MVC project


Theory:
 Search
LO3
 Data validation
Session 23,24 Topic: Adding
Search & Validation
Practice:
 Continue sample MVC project

3
Learning
Sessions Session Activities
Outcome(s)
Theory:
 Explain assignment requirements
LO3  Instruct to do the assignment
Session 25,26 Introduction to
Assignment 2 Practice:
 Carry on assignment: create MVC project and with basic
CRUD entities
Theory:
 Lambda Expressions
LO3  LINQ
Session 27,28 Topic: Lambda
Expression & LINQ Practice:

 Continue assignment 2
Theory:
 Entity Framework and ORMs
 EF Code First
LO3  Configuration and Data Annotation
 Migration
Session 29,30 Topic: Entity
Framework Code
First Practice:

 Continue assignment 2
 Research MVC frameworks
Theory:
 Implementing Authentication
LO3  ASP.NET Identity
 Authorization Process
Session 31,32 Topic:
Authentication and
Authorization Practice:

 Continue assignment 2
 Research MVC frameworks
Theory:
 ASP.NET Web API
LO3
 Web API Controllers
Session 33,34 Topic: ASP.NET
Web API
Practice:
 Review assignment 2

4
Learning
Sessions Session Activities
Outcome(s)
Practice:
LO3  Application development workshop with tutor support to
Session 35,36 Topic: Workshop introduce different MVC frameworks to develop
 Discuss, select or synthesize development methodology for
on Assignment 2
use with the creation of student’s application

LO4 Practice:
Session 37,38  10-15 minutes each student (can do in parallel), present
Code demo
program, answer questions, fix/modify code (if needed)
LO1, LO2, LO3,
LO4 Practice:
Session 39,40  5 minutes each student present: problem-design-
Student
Presentation implementation-result

Bridge Syllabus:

Learning
Sessions Session Activities
Outcome(s)
Theory:
 Introduction to the unit content and unit assessment.
LO1  Requirement concepts and requirement modeling
 Modeling tools
Session 1,2 Topic: Software
Requirement Practice:
Concepts
 Investigate real-world scenario to identify problem
requirements
 Draw use case diagram for the requirements
Theory:
 General Introduction to OOAD
LO1, LO2  Object modeling technique
 Three models
Session 3,4 Topic: Object
Oriented Analysis  Four phases
and Design
Practice:
 Draw class and sequence diagrams

5
Learning
Sessions Session Activities
Outcome(s)
Theory:
LO1, L02  Explain assignment requirements
 Instruct to do the assignment
Session 5,6 Introduction to
Assignment 1 Practice:
 Carry on assignment: analyse application requirements
Theory:
LO2  UML concepts
 Simple analysis/design UML diagrams
Session 7,8 Topic: Unified
Modeling Language
(UML) Practice:
 Carry on assignment 1: design application functions
Practice:
 Review of student progress on the unit assignment
LO1, LO2
 Application development workshop with tutor support to
Session 9,10 Topic: Workshop introduce different design and development methodologies.
on Assignment 1  Discuss, select or synthesize a design and development
methodology for use with the creation of your application

Theory:

 MVC patterns
LO3
 Introduction to ASP. NET MVC Framework
Session 11,12 Topic: Introduction  Razor Engine
to ASP .NET MVC
Practice:

 Review and submit assignment 1


Theory:
 ASP.NET MVC project
 Controller
LO3
 URL Routing
Session 13,14 Topic: Creating  View
APS.NET MVC  Model
application
Practice:

 Create sample MVC project

6
Learning
Sessions Session Activities
Outcome(s)
Theory:
 Explain assignment requirements
LO3  Instruct to do the assignment
Session 15,16 Introduction to
Assignment 2 Practice:
 Carry on assignment: create MVC project and with basic
CRUD entities
Theory:
 Implementing Authentication
LO3  ASP.NET Identity
 Authorization Process
Session 17 Topic:
Authentication and
Authorization Practice:

 Continue assignment 2
 Research MVC frameworks
Theory:
 ASP.NET Web API
LO3
 Web API Controllers
Session 18 Topic: ASP.NET
Web API
Practice:
 Review assignment 2
Practice:
 Application development workshop with tutor support to
LO3, LO4 introduce different MVC frameworks to develop
Session 19 Topic: Workshop  Discuss, select or synthesize development methodology for
on Assignment 2 use with the creation of student’s application
Code demo  10-15 minutes each student (can do in parallel), present
program, answer questions, fix/modify code (if needed)

LO1, LO2, LO3,


LO4 Practice:
Session 20  5 minutes each student present: problem-design-
Student
Presentation implementation-result

You might also like