Features, scenarios and stories
© Ian Sommerville 2018
© Ian Sommerville 2018:
Features, Scenarios and Stories
Software products
2
© Ian Sommerville 2018:
Features, Scenarios and Stories
Software features
3
© Ian Sommerville 2018:
Features, Scenarios and Stories
User understanding
4
© Ian Sommerville 2018:
Features, Scenarios and Stories
Figure 3.1 From personas to features
5
Natural language descriptions of a user interacting with a software product
A way of representing users
Fragments of product functionality
Natural language descriptions of something that is needed or wanted by users
© Ian Sommerville 2018:
Features, Scenarios and Stories
© Ian Sommerville 2018:
Features, Scenarios and Stories
Figure 3.2 Feature description
6
© Ian Sommerville 2018:
Features, Scenarios and Stories
© Ian Sommerville 2018:
Features, Scenarios and Stories
Figure 3.3 The ‘New Group’ feature description
7
© Ian Sommerville 2018:
Features, Scenarios and Stories
© Ian Sommerville 2018:
Features, Scenarios and Stories
Personas
8
© Ian Sommerville 2018:
Features, Scenarios and Stories
Table 3.1 A persona for a primary school teacher
9
Jack, a primary school teacher
Jack, age 32, is a primary school (elementary school) teacher in Ullapool, a large coastal village in the Scottish Highlands. He teaches children from ages 9-12. He was born in a fishing community north of Ullapool, where his father runs a marine fuels supply business and his mother is a community nurse. He has a degree in English from Glasgow University and retrained as a teacher after several years working as a web content author for a large leisure group.
Jack’s experience as a web developer means that he is confident in all aspects of digital technology. He passionately believes that the effective use of digital technologies, blended with face to face teaching, can enhance the learning experience for children. He is particularly interested in using the iLearn system for project-based teaching, where students work together across subject areas on a challenging topic.
© Ian Sommerville 2018:
Features, Scenarios and Stories
© Ian Sommerville 2018:
Features, Scenarios and Stories
Persona descriptions
10
© Ian Sommerville 2018:
Features, Scenarios and Stories
Figure 3.4 Persona descriptions
11
© Ian Sommerville 2018:
Features, Scenarios and Stories
© Ian Sommerville 2018:
Features, Scenarios and Stories
Table 3.2 Aspects of a persona description
12
Personalization
You should give them a name and say something about their personal circumstances. This is important because you shouldn’t think of a persona as a role but as an individual. It is sometimes helpful to use an appropriate stock photograph to represent the person in the persona. Some studies suggest that this helps project teams use personas more effectively.
Job-related�If your product is targeted at business, you should say something about their job and (if necessary) what that job involves. For some jobs, such as a teacher where readers are likely to be familiar with the job, this may not be necessary.
Education�You should describe their educational background and their level of technical skills and experience. This is important, especially for interface design.
Relevance�If you can, you should say why they might be interested in using the product and what they might want to do with it.
© Ian Sommerville 2018:
Features, Scenarios and Stories
© Ian Sommerville 2018:
Features, Scenarios and Stories
Table 3.3 A persona for a history teacher
13
Emma, a history teacher�Emma, age 41, is a history teacher in a secondary school (high school) in Edinburgh. She teaches students from ages 12 to 18. She was born in Cardiff in Wales where both her father and her mother were teachers. After completing a degree in history from Newcastle University, she moved to Edinburgh to be with her partner and trained as a teacher. She has two children, aged 6 and 8, who both attend the local primary school. She likes to get home as early as she can to see her children, so often does lesson preparation, administration and marking from home.
Emma uses social media and the usual productivity applications to prepare her lessons, but is not particularly interested in digital technologies. She hates the virtual learning environment that is currently used in her school and avoids using it if she can. She believes that face-to-face teaching is most effective. She might use the iLearn system for administration and access to historic films and documents. However, she is not interested in a blended digital/face-to-face approach to teaching.
© Ian Sommerville 2018:
Features, Scenarios and Stories
© Ian Sommerville 2018:
Features, Scenarios and Stories
Table 3.4 A persona for an IT technician
14
Elena, a school IT technician�Elena, age 28, is a senior IT technician in a large secondary school (high school) in Glasgow with over 2000 students. Originally from Poland, she has a diploma in electronics from Potsdam University. She moved to Scotland in 2011 after being unemployed for a year after graduation. She has a Scottish partner, no children, and hopes to develop her career in Scotland. She was originally appointed as a junior technician but was promoted, in 2014, to a senior post responsible for all the school computers.
Although not involved directly in teaching, Elena is often called on to help in computer science classes. She is a competent Python programmer and is a ‘power user’ of digital technologies. She has a long-term career goal of becoming a technical expert in digital learning technologies and being involved in their development. She wants to become an expert in the iLearn system and sees it as an experimental platform for supporting new uses for digital learning.
© Ian Sommerville 2018:
Features, Scenarios and Stories
© Ian Sommerville 2018:
Features, Scenarios and Stories
Persona benefits
15
© Ian Sommerville 2018:
Features, Scenarios and Stories
Deriving personas
16
© Ian Sommerville 2018:
Features, Scenarios and Stories
Scenarios
17
© Ian Sommerville 2018:
Features, Scenarios and Stories
Table 3.5 Jack’s scenario:using the iLearn system for class projects
18
Fishing in Ullapool�Jack is a primary school teacher in Ullapool, teaching P6 pupils. He has decided that a class project should be focused around the fishing industry in the area, looking at the history, development and economic impact of fishing.
As part of this, students are asked to gather and share reminiscences from relatives, use newspaper archives and collect old photographs related to fishing and fishing communities in the area. Pupils use an iLearn wiki to gather together fishing stories and SCRAN (a history archive site) to access newspaper archives and photographs. However, Jack also needs a photo-sharing site as he wants students to take and comment on each others’ photos and to upload scans of old photographs that they may have in their families. He needs to be able to moderate posts with photos before they are shared, because pre-teen children can’t understand copyright and privacy issues.
Jack sends an email to a primary school teachers’ group to see if anyone can recommend an appropriate system. Two teachers reply and both suggest that he uses KidsTakePics, a photo-sharing site that allows teachers to check and moderate content. As KidsTakePics is not integrated with the iLearn authentication service, he sets up a teacher and a class account with KidsTakePics.
He uses the the iLearn setup service to add KidsTakePics to the services seen by the students in his class so that, when they log in, they can immediately use the system to upload photos from their phones and class computers.
© Ian Sommerville 2018:
Features, Scenarios and Stories
© Ian Sommerville 2018:
Features, Scenarios and Stories
Figure 3.5 Elements of a scenario description
19
© Ian Sommerville 2018:
Features, Scenarios and Stories
© Ian Sommerville 2018:
Features, Scenarios and Stories
Scenario elements
20
© Ian Sommerville 2018:
Features, Scenarios and Stories
Emma’s scenario
21
© Ian Sommerville 2018:
Features, Scenarios and Stories
Table 3.6 Emma’s scenario: using iLearn for administration
22
Emma is teaching the history of the First World War to a class of 14 year olds (S3). A group of S3 students are visiting the historic World War One battlefields in northern France. She want to set up a ‘battlefields group’ where the students who are attending the trip can share their research about the places they are visiting as well as their pictures and thoughts about the visit.
From home, she logs onto the iLearn system system using her Google account credentials. Emma has two iLearn accounts – her teacher account and a parent account associated with the local primary school. The system recognises that she is a multiple account owner and asks her to select the account to be used. She chooses the teacher account and the system generates her personal welcome screen. As well as her selected applications, this also shows management apps that help teachers create and manage student groups.
Emma selects the ‘group management’ app, which recognizes her role and school from her identity information and creates a new group. The system prompts for the class year (S3) and subject (history) and automatically populates the new group with all S3 students who are studying history. She selects those students going on the trip and adds her teacher colleagues, Jamie and Claire, to the group.
© Ian Sommerville 2018:
Features, Scenarios and Stories
© Ian Sommerville 2018:
Features, Scenarios and Stories
Table 3.6 Emma’s scenario: using iLearn for administration
23
She names the group and confirms that it should be created. The app sets up an icon on her iLearn screen to represent the group, creates an email alias for the group and asks Emma if she wishes to share the group. She shares access with everyone in the group, which means that they also see the icon on their screen. To avoid getting too many emails from students, restricts sharing of the email alias to Jamie and Claire.
The group management app then asksEmma if she wishes to set up a group web page, wiki and blog. Emma confirms that a web page should be created and she types some text to be included on that page.
She then accesses flickr using the icon on her screen, logs in and creates a private group to share trip photos that students and teachers have taken. She uploads some of her own photos from previous trips and emails an invitation to join the photo-sharing group to the Battlefield email list. Emma uploads material from her own laptop that she has written about the trip to iLearn and shares this with the ‘Battlefields Group’. This action adds her documents to the web page and generates an alert to group members that new material is available.
© Ian Sommerville 2018:
Features, Scenarios and Stories
© Ian Sommerville 2018:
Features, Scenarios and Stories
Writing scenarios
24
© Ian Sommerville 2018:
Features, Scenarios and Stories
Table 3.7 Elena’s scenario: configuring the iLearn system
25
Elena has been asked by David, the head of the art department in her school, to help set up an iLearn environment for his department. David wants an environment that includes tools for making and sharing art, access to external websites to study artworks, and ‘exhibition’ facilities so that the students’ work can be displayed.
Elena’s starts by talking to art teachers to discover the tools that they recommend and the art sites that they use for studies. She also discovers that the tools they use and the sites they access vary according to the age of their students. Consequently, different student groups should be presented with a toolset that is appropriate for their age and experience.
Once she has established what is required, Elena logs into the iLearn system as an administrator and starts configuring the art environment using the iLearn setup service. She creates sub-environments for three age groups plus a shared environment that includes tools and sites that may be used by all students.
She drags and drops tools that are available locally and the URLs of external websites into each of these environments. For each of the sub-environments, she assigns an art teacher as its administrator so that they can refine the tool and web site selection that has been set up. She publishes the environments in ‘review mode’ and makes them available to the teachers in the art department.
After discussing the environments with the teachers, Elena shows them how to refine and extend the environments. Once they have agreed that the art environment is useful, it is released to all students in the school.
© Ian Sommerville 2018:
Features, Scenarios and Stories
© Ian Sommerville 2018:
Features, Scenarios and Stories
User involvement
26
© Ian Sommerville 2018:
Features, Scenarios and Stories
User stories
27
© Ian Sommerville 2018:
Features, Scenarios and Stories
User stories in planning
28
© Ian Sommerville 2018:
Features, Scenarios and Stories
Figure 3.6 User stories from Emma’s scenario
29
© Ian Sommerville 2018:
Features, Scenarios and Stories
© Ian Sommerville 2018:
Features, Scenarios and Stories
Feature description using user stories
30
© Ian Sommerville 2018:
Features, Scenarios and Stories
Figure 3.7 User stories describing the Groups feature
31
© Ian Sommerville 2018:
Features, Scenarios and Stories
© Ian Sommerville 2018:
Features, Scenarios and Stories
Stories and scenarios
32
© Ian Sommerville 2018:
Features, Scenarios and Stories
Feature identification
33
© Ian Sommerville 2018:
Features, Scenarios and Stories
Figure 3.8 Feature design
34
© Ian Sommerville 2018:
Features, Scenarios and Stories
© Ian Sommerville 2018:
Features, Scenarios and Stories
Table 3.8 Knowledge required for feature design
User knowledge�You can use user scenarios and user stories to inform the team of what users want and how they might use it the software features.
Product knowledge�You may have experience of existing products or decide to research what these products do as part of your development process. Sometimes, your features have to replicate existing features in these products because they provide fundamental functionality that is always required.
Domain knowledge�This is knowledge of the domain or work area(e.g. finance, event booking) that your product aims to support. By understanding the domain, you can think of new innovative ways of helping users do what they want to do.
Technology knowledge�New products often emerge to take advantage of technological developments since their competitors were launched. If you understand the latest technology, you can design features to make use of it.
35
© Ian Sommerville 2018:
Features, Scenarios and Stories
© Ian Sommerville 2018:
Features, Scenarios and Stories
Figure 3.9 Factors in feature set design
36
© Ian Sommerville 2018:
Features, Scenarios and Stories
© Ian Sommerville 2018:
Features, Scenarios and Stories
Feature trade-offs
37
© Ian Sommerville 2018:
Features, Scenarios and Stories
Feature creep
38
© Ian Sommerville 2018:
Features, Scenarios and Stories
Figure 3.10 Avoiding feature creep
39
© Ian Sommerville 2018:
Features, Scenarios and Stories
© Ian Sommerville 2018:
Features, Scenarios and Stories
Feature derivation
40
© Ian Sommerville 2018:
Features, Scenarios and Stories
Table 3.9 The iLearn system vision
FOR teachers and educators WHO need a way to help students use web-based learning resources and applications, THE iLearn system is an open learning environment THAT allows the set of resources used by classes and students to be easily configured for these students and classes by teachers themselves.
UNLIKE Virtual Learning Environments, such as Moodle, the focus of iLearn is the learning process itself, rather than the administration and management of materials, assessments and coursework. OUR product enables teachers to create subject and age-specific environments for their students using any web-based resources, such as videos, simulations and written materials that are appropriate
41
© Ian Sommerville 2018:
Features, Scenarios and Stories
© Ian Sommerville 2018:
Features, Scenarios and Stories
Features from the product vision
42
© Ian Sommerville 2018:
Features, Scenarios and Stories
Table 3.10 Jack’s scenario with highlighted phrases
43
Jack is a primary school teacher in Ullapool, teaching P6 pupils. He has decided that a class project should be focused around the fishing industry in the area, looking at the history, development and economic impact of fishing.
As part of this, students are asked to gather and share reminiscences from relatives, use newspaper archives and collect old photographs related to fishing and fishing communities in the area. Students use an iLearn wiki to gather together fishing stories and SCRAN (a history archive) to access newspaper archives and photographs. However, Jack also needs a photo-sharing site as he wants pupils to take and comment on each others’ photos and to upload scans of old photographs that they may have in their families. He needs to be able to moderate posts with photos before they are shared, because pre-teen children can’t understand copyright and privacy issues.
Jack sends an email to a primary school teachers’ group, which he is a member of to see if anyone can recommend an appropriate system. Two teachers reply and both suggest that he uses KidsTakePics, a photo-sharing site that allows teachers to check and moderate content. As KidsTakePics is not integrated with the iLearn authentication service, he sets up a teacher and a class account with KidsTakePics.
He uses the the iLearn setup service to add KidsTakePics to the services seen by the students in his class so that when they log in, they can immediately use the system to upload photos from their phones and class computers.
© Ian Sommerville 2018:
Features, Scenarios and Stories
© Ian Sommerville 2018:
Features, Scenarios and Stories
Features from Jack’s scenario
44
© Ian Sommerville 2018:
Features, Scenarios and Stories
The feature list
45
© Ian Sommerville 2018:
Features, Scenarios and Stories
Figure 3.11 The iLearn authentication feature
46
© Ian Sommerville 2018:
Features, Scenarios and Stories
© Ian Sommerville 2018:
Features, Scenarios and Stories
Table 3.11 Feature description using user stories
Description�As a system manager, I want to create and configure an iLearn environment by adding and removing services to/from that environment so that I can create environments for specific purposes.
As a system manager, I want to set up sub-environments that include a subset of services that are included in another environment.
As a system manager, I want to assign administrators to created environments.
As a system manager, I want to limit the rights of environment administrators so that they cannot accidentally or deliberately disrupt the operation of key services.
As a teacher, I want to be able to add services that are not integrated with the iLearn authentication system.
Constraints�The use of some tools may be limited for license reasons so there may be a need to access license management tools during configuration.
Comments�Based on Elena’s and Jack’s scenarios
47
© Ian Sommerville 2018:
Features, Scenarios and Stories
© Ian Sommerville 2018:
Features, Scenarios and Stories
Innovation and feature identification
48
© Ian Sommerville 2018:
Features, Scenarios and Stories
Key points 1
49
© Ian Sommerville 2018:
Features, Scenarios and Stories
Key points 2
50
© Ian Sommerville 2018:
Features, Scenarios and Stories