ADD Review Results

Hello everyone! This evening we had a fast review of our ADD, and we are not very happy with it, because we have to make a lot of changes, it's true that most of all it's changing the structure and renaming the things, but adding that to creating a data model is going to take time (and mostly we don't have much free time left).

Anyway, tomorrow we have a meeting to make most of the changes and delegate the different tasks of the DDD. Hence, we are a little bit stressed with the workload. Besides that, tomorrow is also the team deadline to deliver the briefing work of each member, so we can review before sending it on thursday to the customer.

Apart from that, everything keeps as planned; and we still think that we are doing a good job; so we can be happy with that. And this is a fundamental aspect in the job life of everyone, if you are happy, you work better.

So be happy, my friends LOL

Nieves

Second Stage of Final Deliveries

We have sent the final versions of the URD and SRD to the customer, as with the SPO, CPD, SCMP and SQAP; he must tell us if they have been approved or not.

If they pass, then we are following our schedule and we should not have many problems with keeping a day or so ahead schedule, otherwise I think we are going to be in a huge problem; because the design stage depends on the analysis and if the first one fails, a 'snow-ball' is going to follow with the rest of the work.

Another interesting topic, is that the customer asked 'very nicely' if we could write a briefing on the project, that means how the project is going; with a due date of this week; so obviously our plans have changed and they will appear in the next BPR document.
But I think we have divide the work nicely, becuase it's important all the POVs of the members, so we have decide to explain the project to the customer from each perspective. We will have to wait for his opinion regarding this matter.

Keep checking for updates.

Nieves

Cheer up bloggers!!!

This is a post addressed to the authors of the blog http://agc6.blogspot.com/:

• Mario
• Angel
• Paco
• Jose
  
• Diego
• Fran
• Manu

Cheer up, your work was well done, and as asked by one of your members, this is our attemp to cheer you up.

Have a great time and the good thing is that now you have a little bit more time.

Bye

Architecture Discussion

Hey I know today I am posting a lot of things, but now I have the time. Also this post is about yesterday.

As the application is a web one, we though that a C/S architecture was the best option, and based on what we learned last year we though that our design was a 3-Tier architecture, but yesterday we learnt that it is not a 3-Tier but a 2-Tier. Also, that although the client is part of the architecture, we don't have to refer the client as a component of the architecture because the client is only viewing the code the server is sending.
So the presentation layer is inside the server and it generates the html code for the client.

After that discussion, we have to make changes on the ADD, basically taking out the client component as explained, and other things.

Thinking, we also discussed not to begin the DDD after we have at least a more or less stable version of the ADD with one review, because if we have to make lots of changes in the ADD then the work already done in the DDD would be lost or it could be inconsistent with the changes on the ADD.

So that's what yesterday was about.

We will post our new issues in another moment.

Nieves

Modifications and problems with the analysis!!

Hello, sorry for the delay in the posting, but we've been very busy making changes. We already had the reviews of the URD and SRD and we realized that we had to make a lot of changes because otherwise our architecture was going to be almost impossible to do.
With the URD we didn't have that many problems, but with the URD, most of the performance constraints had to be changed or modified because we couldn't test them and aso it is almost impossible to implement something to check them.
As those two documents affect all the design process, then we had to plan an urgent get together to fix the problems taking into account the trade-offs of the changes and how to overcome them.

Finally we reached an agreement between the parts in how to change the purpose of some requirements and centre the functionality in important aspects and not adding new ones that the delicious does not have.

So with one week of work we have been able to change the analysis stage and create new and better (based on our point of view) deliverables.

Keep in contact

Nieves

We have passed to second phase!!

Hello, we are very happy to know that we have passed to second phase in the blog competition. We really though that we had failed based on the survey, but miracles exists.

We will open a new survey for the second stage of the competition, the final decision will be on 31st of December, so either way we pass or not we will post a message wishing happy new year to everyone, lol.

We will try to improve and keep posting the evolution of the project.

Many thanks to those who vote on us, we will have to invite you to something (good thing we don't know who vote for us, haha).

And finally, for the groups that have not passed: you made a great job, you can comment on our blog if you want.

Bye

Nieves

Opinions!!
Hello people, we have seen that people is voting in our poll. But currently, people is voting that we are not going to pass to second phase.
So we want to know aspects in which we can improve. Thus, not only vote but give us hints to live up to your expectations.

Thanks

Formal English grammar review!!

This evening we had another review done to our deliverable, in this case the SQAP. Usually is Juanmi the one that tries and in most cases throws the mistakes we have done in our faces (remembering the first review); but today it was a native english speaker...
This creates a problem for us, 'cos we are not native english, so we write as best as we can the english expressions. This session has made us realise this.
It is a good thing, mind you, because if we want to work abroad and we have to write reports or papers, we must know these things. But as always, we have to suck up our pride and ego.

So we will try harder next time.

Yours,
Nieves

Group meeting in another pub!!

From this vantage point I apologise for how bad clients our group is. I explain, yesterday we met to do the requirements acquisition in the morning in a libray, but as we didn't finish; we had to meet again in the afternoon in a bar (the libraries are closed on Saturdays' afternoon, why?? ). Anyway, with only two cokes for person and working we were in the pub called 'La eñe' (in Leganés, Madrid) around 5 hours. So from here sorry, but we will acknowledge you on our possible success.

In a positive point of view, we think we did a great acquisition yesterday reaching half hundreds requirements in the first step. All that is left to it, is what will Juanmi think?

Keep in touch
Nieves

Second meeting!!
Ohh this meeting was way better than the first one. At first we were nervous about what Juanmi was going to tell us and the mistakes that he would expose.
Finally they weren't a lot and the changes were minimum and also he told us that it was a very good document. So in summary we congratulated each other in a work well done.

Now our purpose has been keep on the same path with the quality of the work although it's going to be difficult 'cos we have to give two documents with the same deadline and based on those documents all the project will be defined.
Fear and tremble, here comes the Requirements Acquisition!!!

Nieves

Problems and solutions!!
After the fall out of our first proposal, we had to work on two documents at the same time, but we managed.
Sadly, we had to be a bit overworked, but we made all the corrections that our customer told us, following the motto The client is always right!! At the same time, we realised the configuration document and in it, we had to sit down and think the rules and conventions that everybody has to follow; let me tell you it's hardship.
But anyway, we are happy, because we get up after the fall out, we kept working and we are on the road towards the next milestone.

Nieves

Almost off!!!

Today we have discovered life is not easy for a software engineer. No matter how hard do you try not to leave any mistake on your documents, any can be always spotted. And that's what happened today, but many times. Our documents presented a fairly good appearance according to our opinion, but it happened to contain lots of errors.

At least, the document has not been crossed out. However, it is an important drawback to have all those errors, since a revision has been forced and time goes by while we try to present a third document in time. To solve this, we have rearranged our workload to handle the new situation.

A plan has been adopted to solve this situation and we expect to have it solved by Thursday.

There's quite a lot of work to do.

Mariano