Chevron Left
Client Needs and Software Requirements (으)로 돌아가기

앨버타 대학교의 Client Needs and Software Requirements 학습자 리뷰 및 피드백

2,893개의 평가
539개의 리뷰

강좌 소개

This course covers practical techniques to elicit and express software requirements from client interactions....

최상위 리뷰

2016년 7월 5일

Excellent! There is a lot of great practical info you can apply in real life. I would suggest instructors include some more info about SPM in the framework of startups (rather than client framework).

2018년 1월 30일

It is very good knowledge. But my English poor for that, was, sometimes. So was hard to understand and catch information. As a result 90% for grade. It is ok. But it is ok.\n\nViam supervadet vadens

필터링 기준:

Client Needs and Software Requirements 의 533개 리뷰 중 526~533

교육 기관: German D H

2020년 11월 2일

not as well put together as the previous ones - perhaps you should consider breaking it into smaller, manageable pieces.

교육 기관: Sheldon D S

2020년 4월 28일

The material / question sets does appear ambiguous with little context to answer questions confidently.

교육 기관: Cecil R

2018년 6월 27일

The exam questions could have been written more clearly.

교육 기관: Neha P

2020년 5월 2일

Questions in the last assesment were quite confusing

교육 기관: Mikhail K

2015년 12월 27일

Too high level course. Expected more from it.

교육 기관: Néstor d J M G

2016년 3월 23일


교육 기관: Katherine P Z

2016년 9월 14일

Incredibly frustrated by the peer grading system. I've been able to work on the course at relatively fast pace and have now completed all of the lectures, readings, quizzes and test but can't go on to the next course because not enough people have submitted the homework for me to grade. I understand the advantage of being able to "learn from others" but it doesn't outweigh the disadvantage of not being able to work at one's own pace .

교육 기관: Lino J J

2016년 2월 22일

I don't know how useful the ambiguous requirements exercise is when we only have one-way feedback. I also think that the ambiguous requirements exercise is the most important of the course, and the exercise missed the mark.

I would suggest you structure that exercise as a dialogue, where a PM is working with the customer to elicit requirements, and not give us a big long wish-list of functionality. Structured as a dialogue, you can show that a PM would ask, "You said that the game would make noise. When is the first time it makes noise? How often would game noises be made? Does it ever stop? What makes it stop? Why even have the game make noise in the first place? Are there different noises made during the course of game play/"

So, I can't recommend this particular course, and I'm concerned about what the capstone will look like if you give us an assignment where we're to make sense of functionality delivered as a block of text .