At work, I had to take a training class on writing good requirements. Although, not directly involved with writing requirements, my software functional manager believed that it would help us lowly software engineers to identify terrible requirements that make our lives difficult. Once done the training class, I am now able to identify good requirements.
Good requirements are succinct, feasible, and unambiguous.
Tron: Legacy makes a case for good requirements. Flynn says to CLU, "Let's make the perfect world!" Those are terrible requirements. And from there, you have the downfall of the Grid.
Like the seed, I too am
not totally bowled over by Tron: Legacy. The seed notes that the narrative was thin at times. It's like they had the idea of making Tron 2, but never got around to understanding they needed a story for it. If you've seen the original, you've seen most of the latest iteration. Get sucked into the Grid. Check! Play games to the death. Check! Ride light cycles. Check! Hot computer chick. Check! Go to i/o! Check!
Lots of story beats from the original movie showed up in this movie. Problems arose when it tried to find its own way to tell the story. Is this an adventure film? Is this a father-son reunion film? Is this the Matrix? It's all and none and the audience is left to marvel at awesome action set pieces, but can't fathom the main story line. In the original, Tron there was a thread of a plot: get out of the Grid while attempting to find out the mysteries of Encom power. This movie pulled at one too many threads and didn't place one in the forefront. Is this about the Grid or about the younger Flynn finding his father. Is this about father Flynn and his creation? Is this about playing Grid games? It's all and none.
I am a fan of the original. This one gives us something short. Its not as innovative as the original. It needed a better story. I wish we had gotten one.
3 of 5 stars.
Labels: movies, review, software development
