10
votes
Why are software requirements allowed to change if it means more work for software engineers?
Because software engineering isn’t done for some abstract pursuit of software engineering, it’s about building a useful result.
If halfway through the construction of device A you find out that it won’...
- 5,145
5
votes
How Continuous Integration testing deals with software changes
Not all test should experience changes like how you're describing. For example acceptance test cases shouldn't fail if a constructor changes--they should only change when requirements change. Testers ...
- 9,217
4
votes
Why are software requirements allowed to change if it means more work for software engineers?
why are requirements changes allowed to happen
They aren't "allowed" to happen. They happen.
There is simply a non-zero amount of time between the point in time where the requirements are ...
- 104k
4
votes
Are there any techniques for detecting redundancies a stream of changes to a filesystem?
All you have to do is buffer your structured events such that you can look them up by affected path (source and destination, probably).
The actual mechanism for combining any given pair of events ...
- 12.7k
3
votes
When should a team prefer to introduce a change incrementally instead of a complete refactor of the code?
Consistent UI is very important. That's why most, if not all, shops have a "standard" way of doing UI things, even if that standard is de-facto. Often, that standard arises from conventions that ...
- 200k
3
votes
Accepted
How Continuous Integration testing deals with software changes
Continous Integration is a best practice per se, which main goal is to ensure that your code assembles correctly and pass both unit and integration tests.
CI should happen continuously regardless the ...
- 14.8k
3
votes
Why are software requirements allowed to change if it means more work for software engineers?
What do you mean allowed?
Do you think that businesses like inefficiency, or throwing things away? Change is one of the true constants in the world - as is human inability to predict the future.
One ...
- 110k
2
votes
Accepted
Are there any techniques for detecting redundancies a stream of changes to a filesystem?
What you're describing is very similar in code generation & optimization.
A difference is that in code generation copies are not destructive, whereas in your situation, the moves are ...
- 34.4k
2
votes
Accepted
Is it a bad idea to use a Beta warning on an onworking web application?
Releasing a piece of software as not beta should only be done after testing. You will lose most of your customers, when only one GUI element is not working. For example, a well known online clothing ...
- 136
2
votes
Why are software requirements allowed to change if it means more work for software engineers?
There are three reasons for requirements to change:
Documented requirements were incomplete, wrong or inaccurate;
The world continues to change independently of any projects that might be affected;
...
- 80.6k
2
votes
Accepted
How to change a data model
In principe you should have build your code on well encapsulated domain objects. In this case:
The only code that would rely on database attributes would be in the persistence layer/data access ...
- 80.6k
1
vote
How to change a data model
The "nice" thing to do is to post a news item on your website (or whatever channel you use to communicate to the users of your service) that the hasBoyfriend attribute will eventually be ...
1
vote
How Continuous Integration testing deals with software changes
I think the question needs clarifying a little, but there is the kernel of a/some good question(s) here. Taking your points in turn:
When we are developing a software supported by continuous ...
- 9,825
Only top scored, non community-wiki answers of a minimum length are eligible