Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 years ago.
Improve this question
What is the best way to write the system requirement specification. Definition is given to me. project scope is very heavy.
Which model should i approach to get the detailed requirement from the client ?
Which are the common mistakes while gathering information from client and writing specification ?
Help appreciated.
First of all, you have to have a background in requirements engineering. As a start, look at the Volere templates, that help to organize the requirements in a meaningful way. The authors (the Robertsons) have written a book "Mastering the Requirements Process" (ISBN: 978-0321419491), but there are of course a lot of other authors.
There are a lot of techniques to get requirements from the customer, and it depends on how the customer behaves, in which area he is under way, and how much experiences he has there. It is not possible to give here any advice.
I don't think that there is a list of common mistakes that could help you in any way. Get an experienced requirements engineer, and follow his steps.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 2 years ago.
Improve this question
I was searching for new visualization libraries in Python, and I learned about the existence of Pyvista. The examples I've seen look amazing.
I used to work with Mayavi a few years ago, but Pyvista seems very tempting. Are the features in Pyvista really as well-rounded as traditional libraries like Mayavi, etc.?
The question can seem opinion-based, but sometimes new libraries need a few years to become complete. I learned this the hard way with some CAD packages.
I intend to use Mayavi to post-process results from CFD simulations (computational fluid dynamics). Please let me know your opinions.
Thanks in advance,
As PyVista is just a wrapper for VTK it's safe to say that you are not restricted in what is possible.
I found the move from Mayavi to Pyvista really straight forward. The library has a couple of functions that allows you to convert your existing data structure into VTK friendly structures quite easily.
And if you were a fan of Mayavi's pipeline work there is something similar in PyVista where you can add on different things to do plotter.
I hope that helps. Also, join the slack channel if you want to ask any questions / see what other people are using it for.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 4 years ago.
Improve this question
I want to go with Xamarin.Forms project. Now, I am bit confuse for consuming Rest API for this project. Performance matters.
There are many available but can any body please suggest me which should be best for Xamarin.Forms(.Net Standard)?
Microsoft Http Libraries or third party libraries like Refit, RESTSharp, PortableRest, etc.
Please suggest
All of these options are viable. I think the performance differences between these libraries will be marginal. So, it mostly comes down to what you feel comfortable with.
I like to use Refit because it will take a lot of redundant code out of your hands and you just have to focus on the contract. All the code for the actual calls is generated at compile-time (and thus won't impact your performance at runtime).
Also have a look at how well the library is maintained and if it's active. If you choose one that is already inactive for a while, chances are that you will start relying on older software versions which might not be what you want.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
I know this as been asked but couldn't find an answer that I understand...
Some people told me about the main thing are sagas, but it doesn't look such a big advantage to make me spend my bucks on NServiceBus when I already have MSMQ....
That's a little bit like asking "why do I need ASP.NET MVC when I already have HTTP?"... a little tongue-in-cheek, but still with a lot of truth in it.
NServiceBus gives you message serialization, a sensible threading model, routing, and several ready-to-use messaging patterns out of the box.
MSMQ gives you... message queues! And a fairly complicated API with many low level options that give you no real pit of succes...
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
I am starting to learn how to build rest Web service (I come from soap web service).
I'm an intermediate scala programer. I'd like to know as of now, what is the most widespread framework for building Restful Service. But i would also appreciate personal opinion on what is the easiest to use for the task of solely building rest api/web-service, very fast, with a not so complicate learning curve.
Many thanks,
-M-
Play, Scalatra and Spray are all good choices with a reasonable learning curve.
You'll have to look at these (and others), then decide which fits best with your own preferences. It's a very subjective question and there are too many variables for anyone to be able to give a definitive answer.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 years ago.
Improve this question
Developing software solutions which already exist and are available for re-use (either commercial or open-source). AKA "re-inventing the wheel".
Same as above, but your solution being broken. AKA "re-inventing the square wheel".
Developing solutions for problems which do not exist.
Again, I'm interested in a more formal approach, e.g. TRIZ
Doing some research beforehand (1) and investing in solid software architecture (2,3) usually helps :)
When you're planning to develop something you always need to calculate the benefits of doing some and the things like the ROI.
You could read more about this in Agile Estimating and Planning by Mike Cohn
Local Market Research
Internet Research
Google Metrics (Seeing what the Google Count is)