Scribd
Upload
12 views23 pages

BISP Lecture Progress Report 2

The progress report is due on January 24th and should be approximately 2500 words, detailing various components such as problem analysis, IT strategy, critical self-evaluation, and a demo video. It emphasizes the importance of proper referencing, critical analysis, and the inclusion of appendices for additional data. The report will be assessed based on specific criteria, including the clarity of planning and demonstration of progress.

Uploaded by

marik20048
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
12 views23 pages

BISP Lecture Progress Report 2

The progress report is due on January 24th and should be approximately 2500 words, detailing various components such as problem analysis, IT strategy, critical self-evaluation, and a demo video. It emphasizes the importance of proper referencing, critical analysis, and the inclusion of appendices for additional data. The report will be assessed based on specific criteria, including the clarity of planning and demonstration of progress.

Uploaded by

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

Progress report

Deadline!
• Progress report + Demo – 24th of January (Friday)

2
LOs
1. Understand progress report contents
2. Evaluate assessment criteria
3. Have some examples and tips on writing progress report and
preparing demo

3
Why and what
 60% out of 15% (40% for demo video)
 ~ 2500 words;
 ~10 pages including diagrams (excluding appendices)
 Use appendices & tables if over the word limit
 To be submitted to Intranet

4
Problem analysis – 15%
 Strategy, sector, industry, SWOT, PESTL, demand, competitor
 Can use other techniques/tools too
 No any “must have” list, tools to be in context with project

5
IT strategy – 15%
 How solution supports business activity/manual operations
 To implement business strategy
 To determine capability and evolve
 More details and justification than in PID

6
IT
• I T strategy/development strategy for •Four main components of IT strategy:
project – justification of all aspects of your
development in details  Hardware (all physical components &
where it located)
 Software (programs, apps, utilities,
frameworks its distribution over hardware)
 Networking (diagram of hardware/
software and interconnection)
 Data (type of data stored & where;
security)

7
Some tips & hits:
 Overlap with Business strategy
 Use pros & cons in justification
 Use proper referencing & analysis
 Compare your strategy with competitors
 Its OK to draw on your strength

8
IT strategy
 User platform
 Development engines/frameworks
 Programming language
 Databases
 User Interface
 Optimizations (algorithms, OO programming, using classes, stored procedures,
normalization, cross-browser testing/development, cross platform, reusing objects, MVC
structure etc.)

9
Example. User Platform

10
Example - Development
engine/framework

11
Example - Development
engine/framework

12
Example -
Development
engine/framewor
k

13
Example – Programming language

14
Example –
Databases

15
Example – Databases

16
Critical self evaluation & Results – 5%
 Results by now, what data is collected, what are current conclusions
 What part of system are ready (%; increments; list of functionality) [also
assessed with demo video]
 What changed from initial proposal & why
 Mention if you have changed the project
 How scope of project, methodology changed based on initial results
 Conclusion reached so far
 Connected to project plan & objectives

17
Revised schedule – 10%
 What changed in schedule
 Which tasks added/deleted; what was completed/late
 % completed of task – progress bar
 Good to use color coding to show the progress
 Use feedback from PID to demonstrate improved planning
• Your mark is not decreased if you are late through your schedule – assessed your
ability to clearly plan & critically reflect on your planning. But decreased if your
plan is still not specific (like it was in PID)

18
Draft versions of design documents – 15%
 ER diagrams, models, prototypes, interface prototypes, use cases,
DFDs, state diagrams, decision trees
 Includes both business methodology & computing methodology
draft documents
 Results of research (intermediate or final)

19
Appendices:
 Design documents
 Changed work plan
 Data results summary (interviews, questionnaires, observation)
 Tables, diagrams
 Requirements summary

20
Tips
 Be precise, avoid general descriptions
 Use referencing and theories properly
 Demonstrate your progress
 Describe challenges and problems
 Use critical analysis, compare and contrast

21
Demo video – 40%
 Screen & voice recording
 Brief information about the project - purpose, users, project type
 How prototype works and what functionality developed so far - demo
 Backend including your database tables, your software structure in
IDE/framework
 No longer than 10 minutes

22
Reading
• Jelassi T., Enders A. & Martinez-Lopez • https://www.vyond.com/resources/
F.J. (2014) Strategies for e-Business. product- demo-videos-to-inspire-you/ 
Creating value through electronic & 11 examples of demo
mobile commerce. Concepts & cases,
Pearson Education Limited  Chapter 9,
10, 11
• Pearlson K. & Saunders C. (2006)
Managing & Using Information Systems.
A strategic approach. Wiley  Chapter 1,
2
• https://estorm.com.au/news/the-
importance-of-effective- it-strategic-
planning/

23

You might also like