• Keine Ergebnisse gefunden

Software Engineering for Engineers

N/A
N/A
Protected

Academic year: 2022

Aktie "Software Engineering for Engineers"

Copied!
20
0
0

Wird geladen.... (Jetzt Volltext ansehen)

Volltext

(1)

Software Engineering for Engineers

Exercise 3

(2)

Outline

•  Organizational, Announcements

•  FAQ

•  Recapitulation: What did we learn? / What should we be doing right now?

•  Tutorials:

–  Dash Board –  History Browser

•  Q & A

(3)

Organizational

•  Next week, Wednesday, May 13th:

–  10.15 – 11.45 am (s.t.): Lecture

–  15.00 – 16.30 am (s.t.): Lecture instead of Exercise

•  Teaching assistants:

–  Jonas and Max on business trip from May 13

th

until June 2

nd

–  Lecture and Exercise take place as planned!

–  Temporary Replacement:

•  Helmut Naughton, naughton@in.tum.de

•  Florian Schneider, scheidf@in.tum.de

•  Homework 2/3 due date extension: May 20

th

3

(4)

Can you fix this?

•  Client: “The system doesn't work!”

(5)

Frequently asked questions

•  It doesn't work or how to report a bug?

•  How to create users in my project?

•  How to update my client?

•  What is a Functional Requirement, what is a Use Case?

•  My account does not work.

(6)

If you need any help...

•  Website: www.unicase.org

•  Mailinglist: unicase@teambruegge.informatik.tu-muenchen.de

•  Unicase Lab: Room 01.07.43

•  Jonas and Max: Room 01.07.41

(7)

Announcements

7

•  Sprint planning:

–  Assign all action items –  Plan both sprints

•  Requirements will change soon

(8)

Recapitulation: What did we learn last time?

8

(9)

System Model Project Model

UseCase

Class A

Class B

Developer

Analyst

Tester

Manager

Issue Task

Meeting Sprint

Subsystem

?

Unicase

(10)

Project Management Model

(11)

ActionItems und BugReports

85748

(12)

Issues

(13)

Annotation

(14)

WorkPackages

(15)

Work Item Completion States

15

(16)

Predecessor/Successor

(17)

Work Item Open/Blocked States

17

(18)

Dashboard Tutorial

18

(19)

History Browser Tutorial

19

(20)

EMF Tutorial

20

Referenzen

ÄHNLICHE DOKUMENTE

To which extent this tool supports the feature to create security mechanism, or at-least include a feature similar to declare security mechanism in efficient

Die Ergebnisse der Befragung lassen den Schluss zu, dass es durchaus Optimierungs- potential im Requirements-Engineering gibt. Besonders dann, wenn sich der Kunde seiner

– Use upper and lower bounds of the values of the cost function – Upper bound = best found solution for minimization. – Lower bound = If lower bound > upper bound => eliminate

In dem Fall, dass es für einen Benutzer genau einen realen Stakeholder gibt, wird dieser nicht zur Persona, sondern wird weiterhin als Stakeholder betrachtet und in

Gathering and documenting individual end-users’ requirements and contextual information is seen as a first step towards the design and development of Mobile Social Software that

This paper presents selected features of the web platform that illustrate how Social Software concepts might fruitfully complement RE practices in an integrated fashion and

Abstract: Requirements engineering constitutes the bridge between the usage world and the development world of software-intensive systems.. Its responsibility has thus often

He worked for the content industry and does research on citation networks, research evaluation and research software discovery. Alexander is CIO of the Cluster of Excellence –