Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 5 years ago.
Improve this question
I know what is "use case", but I haven't any idea about "E2E" in this context.
What does "E2E use case" mean?
It should be "End to End" Use Case.
As Emil said it means End to End.
As with most terminology it can mean different things from company to company. So always ask your group to explain what they mean with this word.
For me an "End to end use-case" means a list of steps that follow the full process from beginning to end. For example buying some from a web-shop:
Open website
Put stuff in basket
Register a new account
Pay
Receive the order confirmation
Receive the shipping confirmation
Get the actual stuff
In the world of software development I would also add that it uses the full-stack (e.g. from UserInterface till database and back) as it would be in a production environment.
Other reads:
UML E2E use-case example: http://www.modernanalyst.com/Resources/Articles/tabid/115/ID/2017/End-to-End-UML-Use-Case-Diagram.aspx
In my practice 'e2e' means 'End to end test scenarios' and defines business-relates scenarios.
Not checking button is checked only or control contains expected value, but describes real business processes, the value user gets moving through this process.
So this processes should be automated or checked with higher priority than others.
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 1 year ago.
Improve this question
I have to write the "assumptions" part of a pentest report and I am having trouble understanding what I should write. I checked multiple pentest reports (from https://github.com/juliocesarfort/public-pentesting-reports) but none of them had this paragraph. Also I found this explanation "In case there are some assumptions that the pen-tester considers before or during the test, the assumptions need to be clearly shown in the report. Providing the assumption will help the report audiences to understand why penetration testing followed a specific direction.", but still what I do have in mind it is more suited for "attack narative".
Can you provide me a small example (for one action, situation) so I can see exactly how it should be written?
I would think the "assumptions" paragraph and the "Attack narrative" paragraph are somehow overlapping. I would use the "Assumptions" paragraph to state a couple of high level decisions made before starting the attack, with whatever little information the pentester would have on the attack. I would expand on the tools and techniques used in the "Attack narrative" paragraph
For example an assumption could be:
"The pentester is carrying on the exercise against the infrastructure of a soho company with less than 5 people It is common for soho companies to use consumer networking equipment that is usually unsecure, and left configured as defualt. For this reason the attacker focused on scanning for http and ssh using a database of vendors default username and passwords"
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 5 years ago.
Improve this question
For a beginner hobbyist, it seems fairly common to create everything in the order it will be viewed by the user, regardless of its importance, and to intertwine back-end and front-end development.
Obviously, this isn't the most efficient method and would probably be avoided by more experienced developers. I've been exploring different ways to order software development, but I'd like to know if there's a standard that's widely accepted or recommended by the industry.
That is what software development processes are for.
Thing is: there are many different processes; thus there are many different answers to your question.
In 2017, most organisations use processes around the "agile" mindset (or they try to get there), thus your first stop could be Agile software development.
And to give a direct answer to your question:
when you start an agile project, you simply don't know about "all the things the user will view"
instead, you collect requirements
you translate requirements into "user stories"
then the development team and the users (or user representatives) decide on the priority of those user stories
and then, during the development iterations (sprints) a subset of the "most important" user stories is implemented
The key part here: requirements and their priorities are subject to change. The idea to collect everything upfront, to then define an order over all items is simply rejected nowadays.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 5 years ago.
Improve this question
I have a product backlog with some features and a sprint backlog which includes tasks for these features, and also such tasks which are not directly related with stories in product backlog (for example, testing, "to connect to db", "to do interface design" and so on). How can I calculate the velocity then?
You have two options:
Estimate them and treat them as planned work. Not ideal, since these "tasks" don't yield direct value ot the product backlog, but it sounds like work and the product backlog contains all the work that could be done to deliver the product...
Ignore them and treat them as overhead, your velocity will be lower, but that's ok, the velocity then tells you how much work you've been able to deliver that adds value. These other tasks are just "overhead". Or they'd be part of what's commonly called Refinement.
Of course the better solution would be to slice your work in such a way that these tasks are part of delivering the value for that sprint.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I have been asked to design a website for a client as a "side job". I am trying to write up a statement of work for the project. In the past, I have done similar work, and often run into a situation where I believe the work is "done", but the client wants endless tweaks and changes. (As you know, websites are perpetually "under construction").
When you have requirements such as "Design a Home page, design a Contact Us page" how you define a page as "done"?
Don't put anything live, until they accept your work is complete. This should be enough of an incentive for them not to string you along, and allows them to have the quality website they require.
Ask the client to set up a requirements specification for version 1. When you met the requirements contained in this document is your job completed. Everything else belongs to the next version.
In the same situations, I tell my client "you want A, B, C and D. OK, sign here, and we are agreed that the end of application is A-D. Now if you wanted something more in future, it is not a part of our contract, so we'll deal with that in future and of course it has it's own price." This way you make them think before signing and lot's of things become clearer, and lots of needs show up suddenly, but in future they'll either pay more for more needs or won't talk any more :)
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 5 years ago.
Improve this question
We have now installed Agilo to manage our Scrum projects, and we have that proble: we can handle just one backlog. How can we have different backlogs?
Thanks for your time!
Maybe you should try other tools? :)
Here are some other tools you might like to try.
Installable onsite are Rally, Version One. I think Thoughtworks' Mingle is available onsite but they prefer to host it for you.
You may also like to try some of the new online Lean tools: LeanKitKanban, AgileZen.
If possible, get one or more big whiteboards and some post-its, then back it up / produce reports etc. electronically. Excel worked well for this for me. Also there's nothing like the tactile and immediate visual feedback from moving post-its around. You can use index cards and holders or blue-tack if the post-its fall off.
You can also represent the multiple backlogs at different scales; for instance, showing whole features, apps or systems completed at a project or programme level while tracking the smaller stories and tasks at a team level.
Do you have multiple products? There should only be one product backlog for each product - having more than one doesn't make much sense.
To break down a product backlog, it often makes sense to add extra columns to the backlog for different categories within that product. That would make it easier to filter and see different areas of the backlog quickly and efficiently.